FreeBSDwiki - User contributions [en]

Kldunload

2005-08-04T08:30:12Z

Smortex: Speak about kldstat

[[kldunload]] is used to unload kernel modules loaded on the fly using [[kldload]].
To list all loaded modules, use [[kldstat]].

[[Category:System Commands]]

Kldload

2005-08-04T08:28:37Z

Smortex: Speak about kldstat

kldload is used to load kernel modules on the fly.

To list all loaded modules, use [[kldstat]]. To unload a module, use [[kldunload]].

[[Category:System Commands]]

Kldstat

2005-08-04T08:27:17Z

Smortex: Tel what is kldstat useful for

[[kldstat]] is used to list all the modules loaded into the kernel, for example :
shell> '''kldstat'''
Id Refs Address Size Name
1 10 0xc0400000 3e6638 kernel
2 15 0xc07e7000 5d2f0 acpi.ko

Modules take place into ''/boot/kernel/''. They can be loaded using [[kldload]] and removed using [[kldunload]].

[[Category:System Commands]]

Talk:Sound card

2005-08-03T09:01:28Z

Smortex:

Hi !

In order to find your soundcard when you don't know anything about it (In my case, you have your sounddcard integrated into your motherboard and have lost the manual (And maybe is it written somewhere in the BIOS but I have also lost its password ...)), I wrote a shell script that test each driver and tel the user whitch of them are okay for his card.

It is available here (The page is in french, sorry, but the script is written in english for internationnalisation reasons) http://www.astase.com/products/?audio.sh If you thinks it could be usefull to speak about it, you can :) This script is released under the terms of the BSD licence and "expecting to be useful to somebody".

--[[User:Smortex|Smortex]] 05:01, 3 Aug 2005 (EDT)

PostgreSQL

2005-08-03T08:45:38Z

Smortex: Speak about network configuration

PostgreSQL is an open source object-relationnal database management system released under the terms of the BSD licence. It is based on '''postgres''', developped at the University of California at Berkeley Computer Science Department (Juste like [[BSD]]). It features many stuff [[MySQL]] lacks, such as transactional integrity or complex queries.

==Installation==
You can choose to install PostgreSQL from the port tree...

/usr/ports/databases/postgresql80-client
/usr/ports/databases/postgresql80-server

... or the packages ...

pkg_add -r postgresql80-client postgresql80-server

Additionnaly, you may want to install postgresql support to [[PHP]]. Depending on your PHP version, install :

/usr/ports/databases/php4-pgsql
# or
/usr/ports/databases/php5-pgsql

(You can also install it from packages)

==Configuring PostgreSQL==

===Creating a cluster===

What is called cluster in PostgreSQL is the database disk area. The first step is to enable PostgreSQL, witch is done in ''/etc/rc.conf'' : add the following line at the end :
postgresql_enable="YES"

Then, run :
/usr/local/etc/rc.d/010.pgsql.sh initdb

If everything is good, you can now start PostgreSQL :
/usr/local/etc/rc.d/010.pgsql.sh start

===Listening to the network (optionnal)===
By default, you will be able to use your database localy only. Edit the file ''~pgsql/data/postgresql.conf'' and uncomment the following line :
listen_addresses = '*'
You can also change the '''max_connections''' value. Restart PostgreSQL in order to have the changes effective (But you can do the next step before ;-) ).

===Configuring connections (optionnal but recommanded !)===
An other step is required in order to be ready to use PostgreSQL over a network : telling the system ''who'' can access ''what''. This is the role of the ~/data/pg_hba.conf file.
You may want to change some things as the default configuration is to accept all local connections and reject all others. Here we require authentification for a local connection or a connection from the network (192.168.0.xxx) :
#local all all trust
local all all md5
# IPv4 local connections:
#host all all 127.0.0.1/32 trust
host all all 127.0.0.1/32 md5
host all all 192.168.0.1/24 md5

PostgreSQL needs to be restarted after that :
/usr/local/etc/rc.d/010.pgsql.sh restart

===Creating databases===

There are two ways to create databases :
* The '''createdb''' command (in a shell).
* The '''CREATE DATABASE''' query.

For example, let's create the ''foo'' database :

shell> '''psql template1 pgsql'''
Password:
Welcome to psql 8.0.3, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

template1=# '''CREATE DATABASE foo ;'''
CREATE DATABASE
template1=#

Note that the connection is done into the ''template1'' database: This first database is created by the '''initdb''' command and is used to log-in a database for the creation of a new one (Problem of the first database creation).

===Creating users===

There are two ways to create users :
* The '''createuser''' command (in a shell).
* The '''CREATE USER''' query.

Let's create a ''bar'' user :

shell> '''psql template1 pgsql'''
Password:
Welcome to psql 8.0.3, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

template1=# '''CREATE USER bar PASSWORD 'B4R' ;'''
CREATE USER
template1=#
You can change the password of an user like this :
template1=# '''ALTER USER bar PASSWORD 'f0O}b4R' ;'''
ALTER USER
template1=#

==Using PostgreSQL==

Soon ! --[[User:Smortex|Smortex]] 04:45, 3 Aug 2005 (EDT)

==PostgreSQL Website==
[http://www.postgresql.org http://www.postgresql.org]

[[Category : Ports and Packages]]

PostgreSQL

2005-08-03T08:22:00Z

Smortex: Explain user creation

PostgreSQL is an open source object-relationnal database management system released under the terms of the BSD licence. It is based on '''postgres''', developped at the University of California at Berkeley Computer Science Department (Juste like [[BSD]]). It features many stuff [[MySQL]] lacks, such as transactional integrity or complex queries.

==Installation==
You can choose to install PostgreSQL from the port tree...

/usr/ports/databases/postgresql80-client
/usr/ports/databases/postgresql80-server

... or the packages ...

pkg_add -r postgresql80-client postgresql80-server

Additionnaly, you may want to install postgresql support to [[PHP]]. Depending on your PHP version, install :

/usr/ports/databases/php4-pgsql
# or
/usr/ports/databases/php5-pgsql

(You can also install it from packages)

==Configuring PostgreSQL==

===Creating a cluster===

What is called cluster in PostgreSQL is the database disk area. The first step is to enable PostgreSQL, witch is done in ''/etc/rc.conf'' : add the following line at the end :
postgresql_enable="YES"

Then, run :
/usr/local/etc/rc.d/010.pgsql.sh initdb

If everything is good, you can now start PostgreSQL :
/usr/local/etc/rc.d/010.pgsql.sh start

===Creating databases===

There are two ways to create databases :
* The '''createdb''' command (in a shell).
* The '''CREATE DATABASE''' query.

For example, let's create the ''foo'' database :

shell> '''psql template1 pgsql'''
Password:
Welcome to psql 8.0.3, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

template1=# '''CREATE DATABASE foo ;'''
CREATE DATABASE
template1=#

Note that the connection is done into the ''template1'' database: This first database is created by the '''initdb''' command and is used to log-in a database for the creation of a new one (Problem of the first database creation).

===Creating users===

There are two ways to create users :
* The '''createuser''' command (in a shell).
* The '''CREATE USER''' query.

Let's create a ''bar'' user :

shell> '''psql template1 pgsql'''
Password:
Welcome to psql 8.0.3, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

template1=# '''CREATE USER bar PASSWORD 'B4R' ;'''
CREATE USER
template1=#
You can change the password of an user like this :
template1=# '''ALTER USER bar PASSWORD 'f0O}b4R' ;'''
ALTER USER
template1=#

==PostgreSQL Website==
[http://www.postgresql.org http://www.postgresql.org]

[[Category : Ports and Packages]]

PostgreSQL

2005-08-03T08:10:53Z

Smortex: Extrain database creation

PHP

2005-07-19T20:32:57Z

Smortex: corrected a typo in an url

PHP is the recursive acronym for ''PHP Hypertext Preprocessor''. It is an interpreted script language commonly used for dynamic pages generation on webservers. Then it is generaly installed side by side with the [[Apache]] web server, and [[MySQL]] or [[PostgreSQL]] as database management system.

==Installing PHP==

PHP is available trougth the port-tree ...
# cd /usr/ports/lang/php5
... and the packages ...
# pkg_add -r php5

==Using PHP==
There are two ways to use PHP :
* With apache, configured to make PHP to proceed .php files asked by the user.
* As any any interpreter

===PHP for dynamic websites===

All the steps of Apache configuration are explained after PHP installation. You have to add these two lines to httpd.conf:
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps

You will probably also want to add ''index.php'' as a possible directory index:
DirectoryIndex index.html index.php

You have to restart Apache to have your changes effective. For example, if you use Apache 2:
/usr/local/etc/rc.d/apache2 restart

Now, you can try your installation by creating a file test.php:
<?
phpinfo();
?>

Pointing that file with your web browser should show you your php settings.

===Shell scripts in PHP===

You can write shell scripts in PHP, whitch is very useful for ''quick and dirty'' hacks... A PHP shell script looks like this :
#!/usr/local/bin/php
<?
// Your PHP code here ...
echo 'Hello World !\n';
?>

==PHP Website==
[http://www.php.net http://www.php.net]

PHP

2005-07-19T20:31:27Z

Smortex:

PHP is the recursive acronym for ''PHP Hypertext Preprocessor''. It is an interpreted script language commonly used for dynamic pages generation on webservers. Then it is generaly installed side by side with the [[Apache]] web server, and [[MySQL]] or [[PosgreSQL]] as database management system.

==Installing PHP==

PHP is available trougth the port-tree ...
# cd /usr/ports/lang/php5
... and the packages ...
# pkg_add -r php5

==Using PHP==
There are two ways to use PHP :
* With apache, configured to make PHP to proceed .php files asked by the user.
* As any any interpreter

===PHP for dynamic websites===

All the steps of Apache configuration are explained after PHP installation. You have to add these two lines to httpd.conf:
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps

You will probably also want to add ''index.php'' as a possible directory index:
DirectoryIndex index.html index.php

You have to restart Apache to have your changes effective. For example, if you use Apache 2:
/usr/local/etc/rc.d/apache2 restart

Now, you can try your installation by creating a file test.php:
<?
phpinfo();
?>

Pointing that file with your web browser should show you your php settings.

===Shell scripts in PHP===

You can write shell scripts in PHP, whitch is very useful for ''quick and dirty'' hacks... A PHP shell script looks like this :
#!/usr/local/bin/php
<?
// Your PHP code here ...
echo 'Hello World !\n';
?>

==PHP Website==
[http://www.php.net http://www.php.net]

PostgreSQL

2005-07-18T06:17:21Z

Smortex: categorized

PostgreSQL

2005-07-18T06:16:19Z

Smortex:

Talk:Etc/fstab

2005-07-18T05:40:41Z

Smortex:

my apologies, Smortex - I KNEW I already had a page on fstab, it turns out that when I upgraded mediawiki, it decided to suddenly not properly display pages beginning with slashes. Which, of course, was half of this category. =\

I definitely don't want you to feel that your contribution wasn't or isn't appreciated, though. --[[User:Jimbo|Jimbo]] 12:38, 17 Jul 2005 (EDT)

----
----

Okay... Evil MediaWiki ;-)

--[[User:Smortex|Smortex]] 01:40, 18 Jul 2005 (EDT)

Shutdown

2005-07-15T11:52:35Z

Smortex: Tell who can use this command

Used to shutdown a machine. [[shutdown]] requires two arguments: a command and a time. By default, this command is only available to [[root]] and to the members of the '''operator''' group.

==Common Flags and arguments==
'''-h''' will halt the machine
'''-r''' will reboot the machine
'''-p''' will turn the power off after shutdown (only works on some BIOSes)
'''-k''' will send out a message that the machine will reboot, but not actually do it

'''now''' is a valid keyword for the "time" argument.

'''shutdown -h now''' will halt the machine immediately - all users will be logged out forcefully, all pending writes will be performed, all disks sync'd, and the system will halt and wait for reboot.

'''shutdown -h +5''' will broadcast a console message to all currently logged in users warning them that the system will shutdown in 5 minutes, at which time it will forcefully log them out and do so.

'''shutdown -r 0412310000''' will broadcast a console message warning users of a shutdown at midnight on New Year's Eve of 2004 (remember - that means 24 hours before 2005 arrives, not the minute the ball drops!), and at that time will forcefully log them out, halt the system, and automatically reboot.

Compare to [[init]].

[[Category:System Commands]] [[Category:Common Tasks]]

Alias (command)

2005-07-14T22:18:00Z

Smortex: changed a link to a future page

The [[alias]] command is used to create [[aliases]], and to get a list of aliased commands.

==Aliases creation==

The syntax if shell dependant:

'''B-Shell''' ([[sh]], [[bash]]) and '''Z-Shell''' ([[zsh]]) :
alias l=ls
alias la='ls -A'

'''C-Shell''' ([[csh]], [[tcsh]]) :
alias l ls
alias la 'ls -A'

==Special functions==

Some shells provides additionnal features, such as the '''-g''' argument of [[zsh]]'s alias [[built-in]] command. This allow creation of ''global aliases'' :
'''> alias a=aaa'''
'''> alias -g b=bbb'''
'''> echo a b'''
a bbb
This can be very useful :
'''> alias -g ...='../..''''
'''> pwd'''
/foo/bar/misc
'''> cd ...'''
'''> pwd'''
/foo

For more informations on the specific options of your shell, have a look to it's man page.

==Aliases consultation==

You can use this to get an existing [[aliases]] list:
'''> alias'''
...=../..
....=../../..
.....=../../../..
......=../../../../..
.......=../../../../../..
clean='rm -f `find . -name "*~" -o -name ".*~" -o -name ".*.core" -o -name "*.core" -o -name "#*#" -o -name "a.out"`
close='cdcontrol -f /dev/cd0 close'
eject='cdcontrol -f /dev/cd0 eject'
fr='export LANG=fr_FR.ISO8859-15'
la='ls -a'
ll='ls -Al'
ls='ls -FG'
'''> alias ls'''
ls='ls -FG'

See also: [[unalias]], [[which]]

[[Category : System Commands]]

Alias (command)

2005-07-14T22:15:44Z

Smortex: Complete some missing informaitons

The [[alias]] command is used to create [[aliases]], and to get a list of aliased commands.

==Aliases creation==

The syntax if shell dependant:

'''B-Shell''' ([[sh]], [[bash]]) and '''Z-Shell''' ([[zsh]]) :
alias l=ls
alias la='ls -A'

'''C-Shell''' ([[csh]], [[tcsh]]) :
alias l ls
alias la 'ls -A'

==Special functions==

Some shells provides additionnal features, such as the '''-g''' argument of [[zsh]]'s alias [[builtin command]]. This allow creation of ''global aliases'' :
'''> alias a=aaa'''
'''> alias -g b=bbb'''
'''> echo a b'''
a bbb
This can be very useful :
'''> alias -g ...='../..''''
'''> pwd'''
/foo/bar/misc
'''> cd ...'''
'''> pwd'''
/foo

For more informations on the specific options of your shell, have a look to it's man page.

==Aliases consultation==

You can use this to get an existing [[aliases]] list:
'''> alias'''
...=../..
....=../../..
.....=../../../..
......=../../../../..
.......=../../../../../..
clean='rm -f `find . -name "*~" -o -name ".*~" -o -name ".*.core" -o -name "*.core" -o -name "#*#" -o -name "a.out"`
close='cdcontrol -f /dev/cd0 close'
eject='cdcontrol -f /dev/cd0 eject'
fr='export LANG=fr_FR.ISO8859-15'
la='ls -a'
ll='ls -Al'
ls='ls -FG'
'''> alias ls'''
ls='ls -FG'

See also: [[unalias]], [[which]]

[[Category : System Commands]]

Alias (command)

2005-07-13T08:24:50Z

Smortex: Speab about reading alias values

The [[alias]] command is used to create [[aliases]], and to get a list of aliased commands.

==Aliases creaction==

The syntax if shell dependant:

'''B-Shell''' ([[sh]], [[bash]]) :
alias l=ls
alias la='ls -A'

'''C-Shell''' ([[csh]], [[tcsh]]) :
alias l ls
alias la 'ls -A'

==Aliases consultation==

You can use this to get an existing [[aliases]] list:
'''> alias'''
...=../..
....=../../..
.....=../../../..
......=../../../../..
.......=../../../../../..
clean='rm -f `find . -name "*~" -o -name ".*~" -o -name ".*.core" -o -name "*.core" -o -name "#*#" -o -name "a.out"`
close='cdcontrol -f /dev/cd0 close'
eject='cdcontrol -f /dev/cd0 eject'
fr='export LANG=fr_FR.ISO8859-15'
la='ls -a'
ll='ls -Al'
ls='ls -FG'
'''> alias ls'''
ls='ls -FG'

See also: [[unalias]], [[which]]

[[Category : System Commands]]

Unalias

2005-07-13T08:19:21Z

Smortex:

The [[unalias]] command is used to remove an aliased command (make with [[alias]]).

The syntax is always the same : to remove the alias ''foo''
unalias foo

See also: [[alias]]
[[Category : System Commands]]

Alias (command)

2005-07-13T08:16:33Z

Smortex:

The [[alias]] command is used to create [[aliases]].

The syntax if shell dependant :

'''B-Shell''' ([[sh]], [[bash]]) :
alias l=ls
alias la='ls -A'

'''C-Shell''' ([[csh]], [[tcsh]]) :
alias l ls
alias la 'ls -A'

See also: [[unalias]]

[[Category : System Commands]]

Rm

2005-07-12T08:13:35Z

Smortex: Speak a little bit more abour -P

short for '''remove'''. Seriously, be careful when using this. There is no undelete once you've unlinked a file (unless you've aliased [[rm]] to a [[mv]] script that moves files to a trash folder or something -- not recommended because you will eventually find yourself on a system that doesn't have that alias and make a mistake.

==Common flags==

-r recursive -- same as -R
-f force -- do it and damn the consequences
-d directories
-i confirm before delete
-P overwrite files (with 0xFF's, 0x00's, and 0xFF's again) before deleting them
-v be verbose

==About the -P argument==

Use this argument with extreme care : if you yant to remove a file that have hard links, the file '''will be''' overwritten and its contents will be lost, thus not accessible via the links. Example :
$ echo 'Hello World' > foo
$ ln foo bar
$ cat foo bar
Hello World
Hello World
$ rm -P foo
$ cat bar
$ Hey !! where is bar contents ??
Hey, command not found

See also [[rmdir]]
[[Category:System Commands]]

Unlink

2005-07-12T08:07:02Z

Smortex:

This command do exactly the same as [[rm]] : it removes files. If you have read the section about [[links]] you know that one file contents can be read and write throw one or more files thant's to hard links. So the [[unlink]] command is the exact oposite of the [[ln]] command : it removes one link, and if to more links are available for the file contents, it can not be acceeded and will be overwritten by other information.

The number of hard links for a file can displayed by the [[ls]] command.

Note that the C programming language primitive for deleting files is :
unlink()

DEL

2005-07-12T07:58:43Z

Smortex:

Under FreeBSD and other unixlike OSes, the equivalent command is '''[[rm]]''' or '''[[unlink]]''' (The do do the same, and are commonly hard-linked).

[[Category:Windows Equivalents]]

Talk:Portupgrade

2005-07-10T18:09:46Z

Smortex:

note on the rollback: I strongly prefer showing a pipe to grep rather than the -l argument because they both accomplish the same thing, but piping to grep is a universal tool than can be used with any command or process. It's a good habit to learn using tools and skills that are universally applicable as opposed to stuff that's only applicable to one particular task, unless there is some marked advantage to using the more proprietary method of doing things.

If you know of some particularly good reason to use the -l argument instead of piping to grep, by all means let me know here. --[[User:Jimbo|Jimbo]] 19:23, 9 Jul 2005 (EDT)

----
----

The goal is just avoiding to use two processes when only one is needed... More, I tried this :
Script started on Sun Jul 10 11:35:19 2005
# time portversion -l '<' > /dev/null
portversion 1.90s user 0.68s system 86% cpu 3.001 total
# time portversion | grep '<' > /dev/null
portversion 2.68s user 0.88s system 69% cpu 5.102 total
grep '<' > /dev/null 0.00s user 0.00s system 0% cpu 5.100 total
Script done on Sun Jul 10 11:36:23 2005

I do not know how it work internaly, but I gess that the "-l" argument changes the search algorithme.

But I agree with your point of view... grep has to be known by the users !
The "-l" flag may sometimes be preferable, for a low system for example...

----
----

Yah, if I was scripting repeated operations, by all means I'd use the more efficient way. But in general I think the modularity of *nix is actually by far the best thing about it, and I try to do things as modular as possible if there isn't a compelling reason to do otherwise. Even in my own just day-to-day stuff; sure I already know about grep, but still actually using it for everything keeps me in the habit of using it and that's more useful to me than being in the habit of using something that only applies to portversion, y'know? =)

Btw, the difference in efficiency isn't anywhere near as compelling on my systems:

ph34r# /usr/bin/time -h portversion -l '<' > /dev/null
0.88s real 0.70s user 0.18s sys
ph34r# /usr/bin/time -h portversion | grep '<' > /dev/null
0.89s real 0.68s user 0.21s sys

or

blackbox# /usr/bin/time -h portversion -l '<' > /dev/null
1.03s real 0.83s user 0.18s sys
blackbox# /usr/bin/time -h portversion | grep '<' > /dev/null
1.04s real 0.83s user 0.19s sys

On looking again at your times, I notice that the CPU% is quite a bit higher on the faster score. I have a sneaking suspicion a cron job or something kicked in while you were running the second one, so it just didn't get as much processor time and took longer.

--[[User:Jimbo|Jimbo]] 11:52, 10 Jul 2005 (EDT)

----
----

As my load average is about 1.0, I have done my tests 4 or 5 time to check that the result was always the same (it was)... But it may not have incidence on the statistics since they are updating by the kernel when the process is effectively running and collected by the '''time''' command by reading a data structure filled by the ''wait4()'' system call (If I don't remember wrong, '''time''' ''fork()'' itself, ''exec()'' the command and ''wait4()'' for it)...

What I think is that the execution time can be dependant of the number of results : As I might have everyting up to date, i might have the greater difference I can get (all the ports vs. none)...

Well... I have nothing to conclude from this ... All the two methods do the same :)

Rm

2005-07-10T10:13:53Z

Smortex: Correct the -P flag

Cd

2005-07-10T10:08:02Z

Smortex: Add how to go to an user's directory

Under FreeBSD and other unixlike OSes, '''cd''' means just what it does under Windows - "change directory."

The notable differences being that under unixlike OSes a space is required between '''cd''' and the name of the directory to change to and a forward slash '''/''' is used instead of a backward slash '''\'''

C:\Windows> '''cd\stuff''' (windows)
splat# '''cd /stuff''' (unixlike)

C:\Windows> '''cd..''' (windows)
splat# '''cd ..''' (unixlike)

[[cd]] by itself will send you to your home directory, as will '''cd ~'''. '''cd -''' will show you and then change your directory to the last directory you were in, as below:

[dave]@deus /var/log % cd ~
[dave]@deus ~ % pwd
/home/dave
[dave]@deus ~ % cd /etc
[dave]@deus /etc % cd -
/home/dave
[dave]@deus ~ %

==Common Arguments==
.. up one level, e.g., cd .. in /e/foo will take you to /e/
- previous directory
~ home
~username home directory of the user "username"
. the directory I am in. Not used very often with [[cd]] but more often with commands.

[[Category:Windows Equivalents]]

Pkg deinstall

2005-07-10T10:01:22Z

Smortex:

'''pkg_deinstall''' is used to remove installed [[ports]] from the system. '''pkg_deinstall''' first check the port's dependencies : if any port requires the one you want to remove, the deinstallation will fail, and the list of the slave ports will be displayed.

To deinstall a port, type
# pkg_deinstall ThePortToRemove

* You can use the "-r" flag to remove a port and all the ports depending on it.
* You can deinstall several ports at once : "pkg_deinstall foo bar foobar".
** The ports are not removed in the order they are in the commandline but regarding to their dependencies. For example, if "bar" depends on "foo" and "foobar", '''pkg_deinstall''' will remove "foo" and "foobar", and then, "bar".

Talk:Portupgrade

2005-07-10T09:41:57Z

Smortex:

Sbin/nologin

2005-07-09T22:03:42Z

Smortex:

'''nologin''' is a program that logs the user connection (His username and [[tty]]) then exit.

It is generaly used with acounts with reduced privileges.

Ports, Installing

2005-07-09T21:55:45Z

Smortex: Add a few things and speak about pkg_deinstall

See also: [[Ports]]

Installing software in FreeBSD is very easy if you use the ports tree. To use the ports tree you will first need to [[Installing the Ports Tree | install]] it. If you have the ports tree installed on your system you should try and keep it [[Update the ports tree | updated]] with the most recent software.

Remember you can always get help with ports by typing:
> '''man ports'''

To install a specific program you can [[Searching ports | search]] the ports tree to see if there is a port.
> '''cd /usr/ports/'''
> '''make search name=bash
(listing of all the ports that have 'bash' in their '''name''')
> '''make search key=bash'''
(listing of all the ports that have 'bash' anywhere in the '''description''')

The top command will return a number of results that look something like:
Port: bash-2.05b.007_2
Path: /usr/ports/shells/bash2
Info: The GNU Bourne Again Shell
Maint: obrien@FreeBSD.org
B-deps:
R-deps:

This listing tells you where the port you want to install is, in this case it is in shells/bash2. Now there are a number of things you can do to install a port such as
> '''cd /usr/ports/shells/bash2'''
> '''make install'''
(this will download, compile, and install the port and all of its dependencies)
> '''make clean'''
(this will clean up the port directory as well as dependencies after an install)
> '''make distclean'''
(same as clean but will remove the distfiles for the ports aswell)
> '''make fetch'''
(this will just download the source tarball to "/usr/ports/distfiles")
> '''make extract'''
(this will just extract the port to a ./work directory)
> '''make patch'''
(this will just patch the source files)
> '''make depends'''
(this will install (or compile) all of the dependencies of the current port)
> '''make install distclean'''
(commands can be written in sequence like this one to install a port then distclean)

Ports can also be deinstalled easily. A bad method is to do this
> '''cd /usr/ports/shells/bash2'''
> '''make deinstall'''
Avoid this since you can break down other ports. Instead use [[pkg_deinstall]].

If a port can't be deinstalled or installed, verify that it is a port and not a [[Package]]. If it's a port or you're having other problems, see [[Port Install Troubleshooting]]

== External Links ==
[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html FreeBSD Handbook]

[[Category:Common Tasks]]
[[Category:FreeBSD for Workstations]]

Ports tree

2005-07-09T21:50:16Z

Smortex: Remove many things taht were already written

Kldload

2005-07-09T21:14:54Z

Smortex: speak about kldunload

Used to load kernel modules on the fly.

To unload a module, use [[kldunload]].

Kldunload

2005-07-09T21:13:58Z

Smortex:

Used to unload kernel modules loaded on the fly using [[kldload]].

Eot

2005-07-09T21:09:28Z

Smortex:

End Of Transmission

# wall << EOT
Hey ... it is ...
Tea time :)
EOT

[[Category:FreeBSD Terminology]]

Ports tree

2005-07-09T21:02:48Z

Smortex:

The port tree is commonly located in "/usr/ports/". It is composed of a "two level" directory structure containg a few files. Each application has it own directory, for example, [[vim]] is located in "/editors/vim" from the root of the port directory, so commonly, "/usr/ports/editors/vim" from the root of the system.

Each directory contains a few files:
* '''Makefile''': Used for compiling [[ports]].
* '''distinfo''': Contains informations on the files needed to install (To check their integrity).
* '''pkg-descr''': This file tell what is the port.
* '''pkg-plist''': This file lists the binaries installed by the port.
* An optionnal '''files''' folder: Patches applied on the source before compilation.

Installing an application is quite simple. Just go to the application folder and type
# make install clean

But if you are lazy, you can also use [[pkg_install]] :
# pkg_install vim

== What other commands are supported ? ==

* '''make''' without argument will download the source files of the port and its dependancies, extract them, patch them, and compile them.
* '''make fetch''' only fetch the distfiles (the port sources)
* '''make patch''' only patch the source files
* '''make install''' install all the compiled files
* '''make clean''' remove the compiled files (but not the installed files)
* '''make deinstall''' remove a port... do '''*NOT*''' use this directly (see below).

== Dependancies ==

You have nothing to do while installing: dependencies are automaticaly installed. But this is '''*NOT*''' done while uninstalling (uninstalling a port will not deinstall the other that need it), so '''you shall not deinstall port''' directly in the port tree. Instead, use [[pkg_deinstall]].

== Looking for ports ==

You can browse the port tree randomly to find many interesting ports, but you can also search ports using keywords :
# cd /usr/ports ; make search key=MyKeyword
It you want to search a port by name, use this :
# cd /usr/ports ; make search name=PortName

Emacs

2005-07-09T20:41:26Z

Smortex: Add Vim in the editor list

emacs, written by Richard M. Stallman, is a text editor on crack. It has many modules -- sort of like plug-ins -- that allow you to do all sorts of stuff while still editing (e.g., checking your email.) (It should be noted, however, that despite its muscularity it still is primarily a text editor, ''not'' a word processor.) It is difficult to learn to use for most, but those who do often grow enamored of its versatility.

Other text editors commonly found on BSD systems: [[vi]], [[joe]], [[ee]] (aka [[edit]]), [[nano]], [[vim]] and [[pico]].

== Using Emacs ==
=== Commands ===
In the normal editing mode, Emacs behaves just like other text editors: the character keys (''a'', ''b'', ''c'', ''1'', ''2'', ''3'', etc.) insert the corresponding characters, the arrow keys move the editing point, [[backspace]] deletes text, and so forth. Other commands are invoked with [[modifier key|modified keystrokes]], using the [[control key]] and/or the [[meta key]]/[[alt key]]. Every editing command is actually a call to a function in the Emacs Lisp environment. Even a command as simple as typing <code>a</code> to insert the character ''a'' involves calling a function -- in this case, <code>self-insert-command</code>.

Some of the basic commands are shown below. The control key is denoted by a capital ''C'', and the meta or alt key by a capital ''M''.
{|border="1" cellpadding="5" cellspacing="0" align="center"
| '''Command'''
| '''Keystroke'''
| '''Description'''
|-
|<code>forward-word</code>
|<code>M-f</code>
|Move forward past one word.
|-
|<code>undo</code>
|<code>C-/</code>
|Undo last change, and prior changes if pressed repeatedly.
|-
|<code>keyboard-quit</code>
|<code>C-g</code>
|Abort the current command.
|-
|<code>fill-paragraph</code>
|<code>M-q</code>
|[[Word wrap|Wrap]] text in ("fill") a paragraph.
|-
|<code>save-buffer</code>
|<code>C-x C-s</code>
|Save the current text into a file.
|-
|<code>save-buffers-kill-emacs</code>
|<code>C-x C-c</code>
|Offer to save changes, then exit Emacs.
|}
Note that the commands <code>save-buffer</code> and <code>save-buffers-kill-emacs</code> use ''multiple'' modified keystrokes. For example, <code>C-x C-c</code> means: while holding down the control key, press ''x''; then, while holding down the control key, press ''c''. This technique, allowing more commands to be bound to the keyboard than with the use of single keystrokes alone, first appeared in Emacs. It has since made its way into modern code editors like [[Microsoft_Visual_Studio|Visual Studio]].

When Emacs is running a graphical interface, many commands can be invoked from the menubar or toolbar instead of using the keyboard. However, many experienced Emacs users prefer to use the keyboard anyway, because it is faster and more convenient once the necessary keystrokes have been memorized.

Some Emacs commands work by invoking an external program (such as [[ispell]] for spell-checking or [[GNU Compiler Collection|gcc]] for program compilation), parsing the program's output, and displaying the result in Emacs.

==References==
*[[Richard Stallman|Stallman, Richard M.]] (1981). ''EMACS: The Extensible, Customizable, Self-Documenting Display Editor''. Cambridge Massachusetts: MIT. MIT Artificial Intelligence Laboratory publication AIM-519A. [ftp://publications.ai.mit.edu/ai-publications/pdf/AIM-519A.pdf PDF] [http://www.gnu.org/software/emacs/emacs-paper.html HTML]
* Stallman, Richard M. (2002). ''GNU Emacs Manual. 15th edition''. GNU Press ISBN 1-882114-85-X.
*[[Robert J. Chassell|Chassell, Robert J.]] (2004). ''An Introduction to Programming in Emacs Lisp''. GNU Press ISBN 1-882114-56-6.

==External links==
*[http://en.wikipedia.org/wiki/Emacs Wikipedia.org's Emacs article]
*[http://www.gnu.org/software/emacs/emacs.html The GNU Emacs homepage]
*[http://www.xemacs.org/ The XEmacs homepage]
*[http://www.emacswiki.org/ Emacs users' wiki]
*[http://www.multicians.org/mepap.html ''Multics Emacs: The History, Design and Implementation'']
*[http://www.livingtorah.org/~csebold/emacs/why.phtml ''Why I Became An Emacs User'']
*[http://www.finseth.com/~fin/emacs.html List of Emacs implementations]
*[http://www.finseth.com/craft ''The Craft of Text Editing or Emacs for the Modern World'']
*[http://www.jwz.org/doc/emacs-timeline.html An Emacs timeline]
*[http://www.ntu.edu.sg/home5/PG04878518/EmacsName.html The name for Emacs (Humour)]
*[http://www.lisp.org/humor/ai-koans.html Another name-related humor page]

[[Category : Ports and Packages]]
[[Category : System Commands]]

Vim

2005-07-09T20:40:32Z

Smortex: Add "See also"

''Vim'' is a very powerfull text editor. It is an extanded version of [[Vi]] and means ''VI iMprouved''. It supports many features such as syntax highlighting or folding, can keep backup of our files, and many others ...

Note that vim is not part of FreeBSD, you will have to install it before running it. One installed, Your are adviced to copy the file "/usr/local/share/vim/vim63/vimrc_example.vim" into your home directory and rename it ".vimrc".

See also [[vi]], [[ee]] (commonly aliased under FreeBSD as "[[edit]]"), [[joe]], [[nano]], [[pico]], [[vim]] or [[emacs]].

Joe

2005-07-09T20:40:01Z

Smortex: Add "See also"

''Joe'' means ''Joe's Own Editor''. It is an easy to use text editor, so it is not as powerfull as [[Vim]] nor [[Emacs]]. Nevertheless, you may like it if you are discovering the world of Unix.

See also [[vi]], [[ee]] (commonly aliased under FreeBSD as "[[edit]]"), [[joe]], [[nano]], [[pico]], [[vim]] or [[emacs]].

Ports Tree, Updating

2005-07-09T20:39:08Z

Smortex: Add Vim in the editor list

When updating your FreeBSD system, you'll first want to sync your sources to the live sources offered via [[cvs]]. There is a port [[cvsup]] that you can use to update your other ports and source trees if you want. If you hail from a Windows environment, you may think of keeping your sources updated as about the first half of the FreeBSD procedure which corresponds to [[Windows Update]].

== Installing cvsup ==

You'll need to have superuser access, so [[su]] to root and then go to your /usr/ports/net/ directory. There are two versions of cvsup available to you: cvsup and cvsup-without-gui (for systems that don't have or need the cvsup GUI). Pick the one that's most appropriate for you and go into that directory and "make install clean":

dave@samizdata:~% '''su -'''
Password:
samizdata# '''cd /usr/ports/net/'''
samizdata# '''ls | grep cvsup'''
cvsup
cvsup-mirror
cvsup-without-gui

so, let's say this is a headless server and I don't want X11 on it (which it is, and I don't) so:

samizdata# '''cd cvsup-without-gui/'''
samizdata# '''make install clean'''

and you'll get a ''lot'' of lines scrolling by; this is the program compiling.

== So it's installed already, how do I update the ports tree? ==

Not so fast, speed racer. First you need to configure your ''supfile''. Go to /usr/share/examples/cvsup and look through the example files. The easiest way to make a ''supfile'' for your own personal use is to copy the one that want out of the examples and edit it. So from the command line, do a
cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile
and you have just copied the ''ports-supfile'' over to the /root/ directory (root's home directory). Now you'll need to edit that file: use your favorite [[text file editor]] such as [[vi]], [[ee]] (commonly aliased under FreeBSD as "edit"), [[joe]], [[nano]], [[pico]], [[vim]] or [[emacs]] to edit the ''ports-supfile''.

In that file, you'll want to search for a string that says "CHANGE_THIS.freebsd.org" and change that "CHANGE_THIS" to the name of a real CVSup server. You can get a list of the servers at [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-MIRRORS the list of CVSup mirrors on freebsd.org] but they all have the general form of '''cvsup(number).(country).freebsd.org''' such as cvsup1000000.qw.freebsd.org. It will almost always make the process much faster if you choose a mirror nearest you (or the country that you're in, rather.) Save your change to the file and exit your editor. An easy way to do this is to use [[sed]]:

sed s/CHANGE_THIS.FreeBSD.org/cvsup#.FreeBSD.org/g /root/ports-supfile > /root/ports-supfile_complete

substitute a real number instead of # and ''et viola'', you've got a useful ports-supfile, named /root/ports-supfile_complete.

Once that's done, we're ready to actually update the ports. As root, issue this command:

cvsup -g -L2 /root/ports-supfile_complete

In a perfect world, that will always work. The only times when it wont are when you don't have connectivity or the server that you're cvsup-ing against is not allowing connections. Strictly speaking, the ''-g'' command isn't necessary from a command line, since I installed cvsup-without-gui and the ''-g'' switch just makes sure that the GUI stuff in the regular CVSup program doesn't run. Since it isn't installed, I could have not given the switch and the command would have run just the same. The ''-L'' switch will give you error information, as well as a sort of progress-output -- the number next to the L (2 in this case) increases or decreases the verbosity of the output (0 is totally silent and 3 will give you everything you never wanted to read and more.) The last argument of the command is the actual ports-supfile that we made.

== It's updated. Now what? ==

Well, go into /usr/ports and find stuff you want to install!

You may also want to install the very useful port management tool [[portupgrade]], which also installs a program called [[portversion]]. You can use portversion to check your existing installed programs against what is available in the ports tree, and then use [[portupgrade]] to upgrade your existing, old, installed software to the new versions found in the ports tree. Together, cvsup, portversion, and portupgrade allow you to make sure you have the latest version of ANY port in the ports tree, including packages installed with the base FreeBSD install that have been updated since your particular version was released.

See also:
* [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html The FreeBSD Handbook's section on cvsup and updating]
* [[Updating the system]]

[[Category:Common Tasks]]

Nano

2005-07-09T20:38:16Z

Smortex:

[[nano]] is a text editor, like vi or emacs, but less arcane for the newbie. Probably as close as you're going to get (in a text-only editor) to the hot-key combination in other GUI-driven editors (ie, control-Q for quit, etc.) [[nano]] is basically an updated [[pico]] and replaces/replaced [[pico]] on many systems that have/had it. Since the key combinations are visible at the bottom of whatever screen you're on, all you really need to know is that the caret (the '''^''' character) means "press the control key at the same time as the other letter".

See also [[vi]], [[ee]] (commonly aliased under FreeBSD as "[[edit]]"), [[joe]], [[nano]], [[pico]], [[vim]] or [[emacs]].

[[Category : Ports and Packages]]
[[Category : System Commands]]
[[Category : Newbie Friendly]]

Vim

2005-07-09T20:37:32Z

Smortex:

Joe

2005-07-09T20:29:39Z

Smortex:

''Joe'' means ''Joe's Own Editor''. It is an easy to use text editor, so it is not as powerfull as [[Vim]] nor [[Emacs]]. Nevertheless, you may like it if you are discovering the world of Unix.

Fvwm

2005-07-08T20:56:42Z

Smortex:

Fvwm is a lightwight and hightly customizable window manager for X.

You can found it in '''/usr/ports/x11-wm/fvwm2''', or you can use '''pkg_add -r fvwm2''' to install it.

See the [http://www.fvwm.org FVWM website] for more details.
[[Category:FreeBSD for Workstations]]