FreeBSDwiki - User contributions [en]

MySQL, Simple Installation

2004-09-02T20:32:13Z

Pete:

This article will walk you through a simple installation of MySQL server, for usage via localhost in a local environment. (For example, for use in conjunction with Apache and PHP in a web-database related role, with no direct foreign connections to the MySQL server. All connections will be made internally.)

See also: [[MySQL]]

'''Overview'''

For this article, I'll be installing MySQL Server and Client, version 4.0.20 (current in my ports tree.) The steps listed here will very likely work for newer versions available when you read this, but you may want to google to make sure.

'''Install MySQL from ports'''

First, we need to install the port. Make sure you're logged in as [[root]], and as always, update your ports tree with [[CVSUP]] before doing any major software installations.

oyabun# cd /usr/ports/databases/mysql40-server/
oyabun# make install clean BUILD_OPTIMIZED=YES BUILD_STATIC=yes

This will download the source for MySQL Server, compile it optimized for your particular system, and also install mysql40-client, as it is a dependency. This process will very likely take a decent amount of time. ''Oyabun'' is my BSD server, and it's an AthlonXP 2000+, compiling MySQL from source usually takes about 15 - 25 minutes. (Guesstimating, I've never actually timed it.)

When the installation is done, you'll see something very similar to this:

<pre name="I used pre on this because this is a lot of text.">
To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/local/bin/mysqladmin -u root password 'new-password'
/usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr/local ; /usr/local/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/local/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com
mysql:*:88:
You already have a group "mysql", so I will use it.
mysql:*:88:88::0:0:MySQL Daemon:/var/db/mysql:/sbin/nologin
You already have a user "mysql", so I will use it.
Changed home directory of "mysql" to "/var/db/mysql"
===> Compressing manual pages for mysql-server-4.0.20
===> Registering installation for mysql-server-4.0.20
===> SECURITY REPORT:
This port has installed the following files which may act as network
servers and may therefore pose a remote security risk to the system.
/usr/local/bin/ndb_drop_table
/usr/local/bin/ndb_delete_all
/usr/local/libexec/ndbd
/usr/local/bin/ndb_restore
/usr/local/bin/ndb_cpcd
/usr/local/libexec/ndb_mgmd
/usr/local/bin/ndb_select_all
/usr/local/bin/ndb_drop_index
/usr/local/bin/ndb_desc
/usr/local/lib/mysql/libndbclient.so.0
/usr/local/bin/ndb_show_tables
/usr/local/bin/ndb_waiter
/usr/local/bin/ndb_select_count

This port has installed the following startup scripts which may cause
these network services to be started at boot time.
/usr/local/etc/rc.d/mysql-server.sh

If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.

For more information, and contact details about the security
status of this software, see the following webpage:
http://www.mysql.com/
===> Cleaning for mysql-client-4.0.20
===> Cleaning for libtool-1.5.8
===> Cleaning for mysql-server-4.0.20</pre>

The really important parts are those about '''setting a MySQL password for your root account''', and the addition of a mysql group and a mysql user to your base system. You'll notice in my example that I already had a mysql user and group, but you likely won't.

You'll also notice that the install added a startup script to /usr/local/etc/rc.d/, meaning MySQL server will start with every boot now. Let's move on to configuration and finish up this installation.

'''Configuration'''

MySQL is now installed, so let's get it ready for use.

First, we have to start the server. The following assumes you logged in as a regular account, then used [[su]] to become [[root]].

oyabun# exit
exit
> su
Password:
oyabun# /usr/local/etc/rc.d/mysql-server.sh start
mysqloyabun#
oyabun#

It may not be necessary, but I usually exit my root shell and re-login in after major software installations, so the system can find necessary scripts and programs in the path, which the new software may have updated. It costs nothing but a few seconds. Anyway: You'll notice mysql notified you that it started by changing the next shell prompt to "''mysqloyabun#'', where ''oyabun'' = the name of your server.

Now, let's set that root password.

oyabun# /usr/local/bin/mysqladmin -u root password 'new-password'
oyabun# /usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'

Change 'new-password' to whatever you really want use as your password. In the second line, change '''oyabun.n3s.local''' to whatever your current domain qualification is for your server. The MySQL install will tell you - remember, I pulled this example out of the output at end-of-install. If you're copying and pasting this as you go into your putty session or other ssh client, WATCH OUT FOR LINEBREAKS. If you copy the carriage return as well, you really did just set your password to 'new-password.' (Hey, don't laugh, it just happened to me.)

If that happens, you'll have to issue a slightly different command to change a current password.

oyabun# /usr/local/bin/mysqladmin -p password 'the-REAL-password'
Enter password:
oyabun#

Since you're logged in as root, this will change your password '''after''' you enter the current password, which if you screwed up like I did, is/was 'new-password'. Crisis averted.

'''Note''': From now on, you can't type '''mysql''' at a command prompt to enter the mysql client, you have to add '''-p''' to make it challenge you for a password.

'''Testing the installation'''

We're going to get into a little bit of mysql syntax here. For more in-depth documentation, you should visit http://www.mysql.com or google the particular command you're having trouble with, using 'mysql grant syntax' as the search argument for example.

oyabun# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 31 to server version: 4.0.20
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> create database testing;
Query OK, 1 row affected (0.00 sec)
mysql> grant all on testing.* to 'user'@'localhost' identified by 'password';
Query OK, 0 rows affected (0.02 sec)
mysql>

First, you'll notice that all commands in the mysql client have to be terminated with ''';'''. If you forget and hit enter, you can just enter a lone ''';''' on a new line, and it will work provided the syntax of the command is correct.

If both of those commands worked, then you just created a database named testing, and assigned full read/write priviledges to a user name 'user' with password 'password'.

To delete a database, issue the following command:

mysql> drop database testing;
Query OK, 0 rows affected (0.00 sec)

That's it! You now have MySQL added to your machine, and you begin using php scripts or other MySQL tools.

[[Category : Ports and Packages]]

MySQL, Simple Installation

2004-09-02T20:27:34Z

Pete:

This article will walk you through a simple installation of MySQL server, for usage via localhost in a local environment. (For example, for use in conjunction with Apache and PHP in a web-database related role, with no direct foreign connections to the MySQL server. All connections will be made internally.)

See also: [[MySQL]]

'''Overview'''

For this article, I'll be installing MySQL Server and Client, version 4.0.20 (current in my ports tree.) The steps listed here will very likely work for newer versions available when you read this, but you may want to google to make sure.

'''Install MySQL from ports'''

First, we need to install the port. Make sure you're logged in as [[root]], and as always, update your ports tree with [[CVSUP]] before doing any major software installations.

oyabun# cd /usr/ports/databases/mysql40-server/
oyabun# make install clean BUILD_OPTIMIZED=YES BUILD_STATIC=yes

This will download the source for MySQL Server, compile it optimized for your particular system, and also install mysql40-client, as it is a dependency. This process will very likely take a decent amount of time. ''Oyabun'' is my BSD server, and it's an AthlonXP 2000+, compiling MySQL from source usually takes about 15 - 25 minutes. (Guesstimating, I've never actually timed it.)

When the installation is done, you'll see something very similar to this:

<pre name="I used pre on this because this is a lot of text.">
To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/local/bin/mysqladmin -u root password 'new-password'
/usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr/local ; /usr/local/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/local/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com
mysql:*:88:
You already have a group "mysql", so I will use it.
mysql:*:88:88::0:0:MySQL Daemon:/var/db/mysql:/sbin/nologin
You already have a user "mysql", so I will use it.
Changed home directory of "mysql" to "/var/db/mysql"
===> Compressing manual pages for mysql-server-4.1.3
===> Registering installation for mysql-server-4.1.3
===> SECURITY REPORT:
This port has installed the following files which may act as network
servers and may therefore pose a remote security risk to the system.
/usr/local/bin/ndb_drop_table
/usr/local/bin/ndb_delete_all
/usr/local/libexec/ndbd
/usr/local/bin/ndb_restore
/usr/local/bin/ndb_cpcd
/usr/local/libexec/ndb_mgmd
/usr/local/bin/ndb_select_all
/usr/local/bin/ndb_drop_index
/usr/local/bin/ndb_desc
/usr/local/lib/mysql/libndbclient.so.0
/usr/local/bin/ndb_show_tables
/usr/local/bin/ndb_waiter
/usr/local/bin/ndb_select_count

This port has installed the following startup scripts which may cause
these network services to be started at boot time.
/usr/local/etc/rc.d/mysql-server.sh

If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.

For more information, and contact details about the security
status of this software, see the following webpage:
http://www.mysql.com/
===> Cleaning for mysql-client-4.0.20
===> Cleaning for libtool-1.5.8
===> Cleaning for mysql-server-4.0.20</pre>

The really important parts are those about '''setting a MySQL password for your root account''', and the addition of a mysql group and a mysql user to your base system. You'll notice in my example that I already had a mysql user and group, but you likely won't.

You'll also notice that the install added a startup script to /usr/local/etc/rc.d/, meaning MySQL server will start with every boot now. Let's move on to configuration and finish up this installation.

'''Configuration'''

MySQL is now installed, so let's get it ready for use.

First, we have to start the server. The following assumes you logged in as a regular account, then used [[su]] to become [[root]].

oyabun# exit
exit
> su
Password:
oyabun# /usr/local/etc/rc.d/mysql-server.sh start
mysqloyabun#
oyabun#

It may not be necessary, but I usually exit my root shell and re-login in after major software installations, so the system can find necessary scripts and programs in the path, which the new software may have updated. It costs nothing but a few seconds. Anyway: You'll notice mysql notified you that it started by changing the next shell prompt to "''mysqloyabun#'', where ''oyabun'' = the name of your server.

Now, let's set that root password.

oyabun# /usr/local/bin/mysqladmin -u root password 'new-password'
oyabun# /usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'

Change 'new-password' to whatever you really want use as your password. In the second line, change '''oyabun.n3s.local''' to whatever your current domain qualification is for your server. The MySQL install will tell you - remember, I pulled this example out of the output at end-of-install. If you're copying and pasting this as you go into your putty session or other ssh client, WATCH OUT FOR LINEBREAKS. If you copy the carriage return as well, you really did just set your password to 'new-password.' (Hey, don't laugh, it just happened to me.)

If that happens, you'll have to issue a slightly different command to change a current password.

oyabun# /usr/local/bin/mysqladmin -p password 'the-REAL-password'
Enter password:
oyabun#

Since you're logged in as root, this will change your password '''after''' you enter the current password, which if you screwed up like I did, is/was 'new-password'. Crisis averted.

'''Note''': From now on, you can't type '''mysql''' at a command prompt to enter the mysql client, you have to add '''-p''' to make it challenge you for a password.

'''Testing the installation'''

We're going to get into a little bit of mysql syntax here. For more in-depth documentation, you should visit http://www.mysql.com or google the particular command you're having trouble with, using 'mysql grant syntax' as the search argument for example.

oyabun# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 31 to server version: 4.0.20
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> create database testing;
Query OK, 1 row affected (0.00 sec)
mysql> grant all on testing.* to 'user'@'localhost' identified by 'password';
Query OK, 0 rows affected (0.02 sec)
mysql>

First, you'll notice that all commands in the mysql client have to be terminated with ''';'''. If you forget and hit enter, you can just enter a lone ''';''' on a new line, and it will work provided the syntax of the command is correct.

If both of those commands worked, then you just created a database named testing, and assigned full read/write priviledges to a user name 'user' with password 'password'.

To delete a database, issue the following command:

mysql> drop database testing;
Query OK, 0 rows affected (0.00 sec)

That's it! You now have MySQL added to your machine, and you begin using php scripts or other MySQL tools.

[[Category : Ports and Packages]]

MySQL, Simple Installation

2004-09-02T20:26:58Z

Pete:

This article will walk you through a simple installation of MySQL server, for usage via localhost in a local environment. (For example, for use in conjunction with Apache and PHP in a web-database related role, with no direct foreign connections to the MySQL server. All connections will be made internally.)

See also: [[MySQL]]

'''Overview'''

For this article, I'll be installing MySQL Server and Client, version 4.0.x (current in my ports tree.) The steps listed here will very likely work for newer versions available when you read this, but you may want to google to make sure.

'''Install MySQL from ports'''

First, we need to install the port. Make sure you're logged in as [[root]], and as always, update your ports tree with [[CVSUP]] before doing any major software installations.

oyabun# cd /usr/ports/databases/mysql40-server/
oyabun# make install clean BUILD_OPTIMIZED=YES BUILD_STATIC=yes

This will download the source for MySQL Server, compile it optimized for your particular system, and also install mysql40-client, as it is a dependency. This process will very likely take a decent amount of time. ''Oyabun'' is my BSD server, and it's an AthlonXP 2000+, compiling MySQL from source usually takes about 15 - 25 minutes. (Guesstimating, I've never actually timed it.)

When the installation is done, you'll see something very similar to this:

<pre name="I used pre on this because this is a lot of text.">
To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/local/bin/mysqladmin -u root password 'new-password'
/usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr/local ; /usr/local/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/local/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com
mysql:*:88:
You already have a group "mysql", so I will use it.
mysql:*:88:88::0:0:MySQL Daemon:/var/db/mysql:/sbin/nologin
You already have a user "mysql", so I will use it.
Changed home directory of "mysql" to "/var/db/mysql"
===> Compressing manual pages for mysql-server-4.1.3
===> Registering installation for mysql-server-4.1.3
===> SECURITY REPORT:
This port has installed the following files which may act as network
servers and may therefore pose a remote security risk to the system.
/usr/local/bin/ndb_drop_table
/usr/local/bin/ndb_delete_all
/usr/local/libexec/ndbd
/usr/local/bin/ndb_restore
/usr/local/bin/ndb_cpcd
/usr/local/libexec/ndb_mgmd
/usr/local/bin/ndb_select_all
/usr/local/bin/ndb_drop_index
/usr/local/bin/ndb_desc
/usr/local/lib/mysql/libndbclient.so.0
/usr/local/bin/ndb_show_tables
/usr/local/bin/ndb_waiter
/usr/local/bin/ndb_select_count

This port has installed the following startup scripts which may cause
these network services to be started at boot time.
/usr/local/etc/rc.d/mysql-server.sh

If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.

For more information, and contact details about the security
status of this software, see the following webpage:
http://www.mysql.com/
===> Cleaning for mysql-client-4.0.20
===> Cleaning for libtool-1.5.8
===> Cleaning for mysql-server-4.0.20</pre>

The really important parts are those about '''setting a MySQL password for your root account''', and the addition of a mysql group and a mysql user to your base system. You'll notice in my example that I already had a mysql user and group, but you likely won't.

You'll also notice that the install added a startup script to /usr/local/etc/rc.d/, meaning MySQL server will start with every boot now. Let's move on to configuration and finish up this installation.

'''Configuration'''

MySQL is now installed, so let's get it ready for use.

First, we have to start the server. The following assumes you logged in as a regular account, then used [[su]] to become [[root]].

oyabun# exit
exit
> su
Password:
oyabun# /usr/local/etc/rc.d/mysql-server.sh start
mysqloyabun#
oyabun#

It may not be necessary, but I usually exit my root shell and re-login in after major software installations, so the system can find necessary scripts and programs in the path, which the new software may have updated. It costs nothing but a few seconds. Anyway: You'll notice mysql notified you that it started by changing the next shell prompt to "''mysqloyabun#'', where ''oyabun'' = the name of your server.

Now, let's set that root password.

oyabun# /usr/local/bin/mysqladmin -u root password 'new-password'
oyabun# /usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'

Change 'new-password' to whatever you really want use as your password. In the second line, change '''oyabun.n3s.local''' to whatever your current domain qualification is for your server. The MySQL install will tell you - remember, I pulled this example out of the output at end-of-install. If you're copying and pasting this as you go into your putty session or other ssh client, WATCH OUT FOR LINEBREAKS. If you copy the carriage return as well, you really did just set your password to 'new-password.' (Hey, don't laugh, it just happened to me.)

If that happens, you'll have to issue a slightly different command to change a current password.

oyabun# /usr/local/bin/mysqladmin -p password 'the-REAL-password'
Enter password:
oyabun#

Since you're logged in as root, this will change your password '''after''' you enter the current password, which if you screwed up like I did, is/was 'new-password'. Crisis averted.

'''Note''': From now on, you can't type '''mysql''' at a command prompt to enter the mysql client, you have to add '''-p''' to make it challenge you for a password.

'''Testing the installation'''

We're going to get into a little bit of mysql syntax here. For more in-depth documentation, you should visit http://www.mysql.com or google the particular command you're having trouble with, using 'mysql grant syntax' as the search argument for example.

oyabun# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 31 to server version: 4.0.20
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> create database testing;
Query OK, 1 row affected (0.00 sec)
mysql> grant all on testing.* to 'user'@'localhost' identified by 'password';
Query OK, 0 rows affected (0.02 sec)
mysql>

First, you'll notice that all commands in the mysql client have to be terminated with ''';'''. If you forget and hit enter, you can just enter a lone ''';''' on a new line, and it will work provided the syntax of the command is correct.

If both of those commands worked, then you just created a database named testing, and assigned full read/write priviledges to a user name 'user' with password 'password'.

To delete a database, issue the following command:

mysql> drop database testing;
Query OK, 0 rows affected (0.00 sec)

That's it! You now have MySQL added to your machine, and you begin using php scripts or other MySQL tools.

[[Category : Ports and Packages]]

MySQL, Simple Installation

2004-09-01T17:37:48Z

Pete:

This article will walk you through a simple installation of MySQL server, for usage via localhost in a local environment. (For example, for use in conjunction with Apache and PHP in a web-database related role, with no direct foreign connections to the MySQL server. All connections will be made internally.)

See also: [[MySQL]]

'''Overview'''

For this article, I'll be installing MySQL Server and Client, version 4.1.x (current in my ports tree.) The steps listed here will very likely work for newer versions available when you read this, but you may want to google to make sure.

'''Install MySQL from ports'''

First, we need to install the port. Make sure you're logged in as [[root]], and as always, update your ports tree with [[CVSUP]] before doing any major software installations.

oyabun# cd /usr/ports/databases/mysql41-server/
oyabun# make install clean BUILD_OPTIMIZED=YES BUILD_STATIC=yes

This will download the source for MySQL Server, compile it optimized for your particular system, and also install mysql41-client, as it is a dependency. This process will very likely take a decent amount of time. ''Oyabun'' is my BSD server, and it's an AthlonXP 2000+, compiling MySQL from source usually takes about 15 - 25 minutes. (Guesstimating, I've never actually timed it.)

When the installation is done, you'll see something very similar to this:

<pre name="I used pre on this because this is a lot of text.">
To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/local/bin/mysqladmin -u root password 'new-password'
/usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr/local ; /usr/local/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/local/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com
mysql:*:88:
You already have a group "mysql", so I will use it.
mysql:*:88:88::0:0:MySQL Daemon:/var/db/mysql:/sbin/nologin
You already have a user "mysql", so I will use it.
Changed home directory of "mysql" to "/var/db/mysql"
===> Compressing manual pages for mysql-server-4.1.3
===> Registering installation for mysql-server-4.1.3
===> SECURITY REPORT:
This port has installed the following files which may act as network
servers and may therefore pose a remote security risk to the system.
/usr/local/bin/ndb_drop_table
/usr/local/bin/ndb_delete_all
/usr/local/libexec/ndbd
/usr/local/bin/ndb_restore
/usr/local/bin/ndb_cpcd
/usr/local/libexec/ndb_mgmd
/usr/local/bin/ndb_select_all
/usr/local/bin/ndb_drop_index
/usr/local/bin/ndb_desc
/usr/local/lib/mysql/libndbclient.so.0
/usr/local/bin/ndb_show_tables
/usr/local/bin/ndb_waiter
/usr/local/bin/ndb_select_count

This port has installed the following startup scripts which may cause
these network services to be started at boot time.
/usr/local/etc/rc.d/mysql-server.sh

If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.

For more information, and contact details about the security
status of this software, see the following webpage:
http://www.mysql.com/
===> Cleaning for mysql-client-4.1.3
===> Cleaning for libtool-1.5.8
===> Cleaning for mysql-server-4.1.3</pre>

The really important parts are those about '''setting a MySQL password for your root account''', and the addition of a mysql group and a mysql user to your base system. You'll notice in my example that I already had a mysql user and group, but you likely won't.

You'll also notice that the install added a startup script to /usr/local/etc/rc.d/, meaning MySQL server will start with every boot now. Let's move on to configuration and finish up this installation.

'''Configuration'''

MySQL is now installed, so let's get it ready for use.

First, we have to start the server. The following assumes you logged in as a regular account, then used [[su]] to become [[root]].

oyabun# exit
exit
> su
Password:
oyabun# /usr/local/etc/rc.d/mysql-server.sh start
mysqloyabun#
oyabun#

It may not be necessary, but I usually exit my root shell and re-login in after major software installations, so the system can find necessary scripts and programs in the path, which the new software may have updated. It costs nothing but a few seconds. Anyway: You'll notice mysql notified you that it started by changing the next shell prompt to "''mysqloyabun#'', where ''oyabun'' = the name of your server.

Now, let's set that root password.

oyabun# /usr/local/bin/mysqladmin -u root password 'new-password'
oyabun# /usr/local/bin/mysqladmin -u root -h oyabun.n3s.local password 'new-password'

Change 'new-password' to whatever you really want use as your password. In the second line, change '''oyabun.n3s.local''' to whatever your current domain qualification is for your server. The MySQL install will tell you - remember, I pulled this example out of the output at end-of-install. If you're copying and pasting this as you go into your putty session or other ssh client, WATCH OUT FOR LINEBREAKS. If you copy the carriage return as well, you really did just set your password to 'new-password.' (Hey, don't laugh, it just happened to me.)

If that happens, you'll have to issue a slightly different command to change a current password.

oyabun# /usr/local/bin/mysqladmin -p password 'the-REAL-password'
Enter password:
oyabun#

Since you're logged in as root, this will change your password '''after''' you enter the current password, which if you screwed up like I did, is/was 'new-password'. Crisis averted.

'''Note''': From now on, you can't type '''mysql''' at a command prompt to enter the mysql client, you have to add '''-p''' to make it challenge you for a password.

'''Testing the installation'''

We're going to get into a little bit of mysql syntax here. For more in-depth documentation, you should visit http://www.mysql.com or google the particular command you're having trouble with, using 'mysql grant syntax' as the search argument for example.

oyabun# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 31 to server version: 4.1.3-beta
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> create database testing;
Query OK, 1 row affected (0.00 sec)
mysql> grant all on testing.* to 'user'@'localhost' identified by 'password';
Query OK, 0 rows affected (0.02 sec)
mysql>

First, you'll notice that all commands in the mysql client have to be terminated with ''';'''. If you forget and hit enter, you can just enter a lone ''';''' on a new line, and it will work provided the syntax of the command is correct.

If both of those commands worked, then you just created a database named testing, and assigned full read/write priviledges to a user name 'user' with password 'password'.

To delete a database, issue the following command:

mysql> drop database testing;
Query OK, 0 rows affected (0.00 sec)

That's it! You now have MySQL added to your machine, and you begin using php scripts or other MySQL tools.

[[Category : Ports and Packages]]

MySQL

2004-09-01T16:38:25Z

Pete:

This article is the main portal for all things MySQL at The BSD Wiki.

See also: [[MySQL_Simple_Installation]]

[[Category : Ports and Packages]]

MySQL

2004-09-01T16:38:13Z

Pete:

This article is the main portal for all things MySQL at The BSD Wiki.

See also: MySQL_Simple_Installation

[[Category : Ports and Packages]]

Talk:ATTRIB

2004-08-25T19:00:54Z

Pete:

Rename this "Attrib"

oops. --[[User:Jimbo|Jimbo]] 18:58, 25 Aug 2004 (GMT)

PWN3D <3

DIR

2004-08-25T18:58:49Z

Pete:

Under FreeBSD and other unix-like OSes, the equivalent command is [[ls]].

[[ls]] is best combined with [[grep]] if you plan on doing any filtering.

Windows:

dir *.txt

Unix:

ls | grep .txt

Windows:

dir boogy*.*

Unix:

ls | grep boogy

[[Category:Windows Equivalents]]

Talk:ATTRIB

2004-08-25T18:56:24Z

Pete:

Rename this "Attrib"

User:Dave

2004-08-25T18:54:51Z

Pete:

I do some unix, linux and BSD stuff for a university in South Florida.

I have broccoli in my socks. Does that make you randy?

Portupgrade

2004-08-25T05:34:02Z

Pete:

'''portupgrade and you'''

portupgrade is a small collection of tools that goes hand in hand with [[cvsup]]. Portupgrade does what it says - upgrades your ports - but it actually means your ''installed'' ports, even packages that were installed as part of the base system. Portupgrade includes two important programs - ''portupgrade'', and [[portversion]]. Between them and cvsup, you'll have the ability to keep all installed software on your system up to date, so long as it exists in the ports tree.

See also - [[cvsup]] - [[Update_the_ports_tree]] - [[portversion]]

== Installing the Portupgrade suite ==

Installation is very simple:

<pre>> su
Enter password:
oyabun# cd /usr/ports/sysutils/portupgrade
oyabun# make install clean</pre>

Once it's done, you'll have to ''exit and re-enter'' your session as [[root]] to use it without typing full pathnames. This assumes you used [[su]] to become root from a different account. If you logged in from the physical console as root, you can exit and re-login, or you can simply su to a new shell. (Lazy!)

== Using portupgrade and portversion ==

Now that that's done, you need to update your ports database.

<pre>oyabun# portsdb -Uu</pre>

This will likely take a while.

Now you can use [[portversion]] to see a list of installed programs that are out of date like so:

<pre>oyabun# portversion | grep '<'
expat <
ezm3 <
fontconfig <
freetype2 <
imake <
libnet-devel <
libtool <
oyabun#</pre>

This is a possible example of the output you'd recieve from portversion. Issuing a portversion command without the ''| grep '<''' would produce a list of ALL installed packages on your machine, with '''<''' for "out of date", '''=''' for "current", and '''>''' for "newer". How can you get "newer" than what's in the ports tree? This happens if you haven't issued a '''portsdb -Uu''' command to update your ports database. The database contains entries pointing to older versions, while the ports tree itself contains newer versions, leading to situations where portversion reports ">".

Now, to upgrade one of these packages, do this:

<pre>oyabun# portupgrade imake</pre>

Portupgrade will upgrade the port with the newer version available in the ports tree, and also take care of any dependencies the new version may have - if it needed ANOTHER installed port upgraded to a newer version, for example.

That's it. You'll have to repeat these steps (portversion, then portupgrade on one of the results) a few times to complete update your software, but all in all it's fairly simple and straightforward.

Note - you may sometimes be prompted to run '''pkgdb -F''' to fix inconsistencies with listed dependencies within programs when you issue portversion commands, after upgrading ports. Just do it ('''pkgdb -F''', that is) and it will take care of the problem, allowing you to issue the portversion command.

User:Pete

2004-08-25T05:31:55Z

Pete:

Portupgrade

2004-08-25T04:14:45Z

Pete:

'''portupgrade and you'''

portupgrade is a small collection of tools that goes hand in hand with [[cvsup]]. Portupgrade does what it says - upgrades your ports - but it actually means your ''installed'' ports, even packages that were installed as part of the base system. Portupgrade includes two important programs - ''portupgrade'', and [[portversion]]. Between them and cvsup, you'll have the ability to keep all installed software on your system up to date, so long as it exists in the ports tree.

See also - [[cvsup]] - [[Update_the_ports_tree]] - [[portversion]]

== Installing the Portupgrade suite ==

Installation is very simple:

<pre>> su
Enter password:
oyabun# cd /usr/ports/sysutils/portupgrade
oyabun# make install clean</pre>

Once it's done, you'll have to ''exit and re-enter'' your session as [[superuser]] to use it without typing full pathnames. This assumes you used [[su]] to become root from a different account. If you logged in from the physical console as root, you can exit and re-login, or you can simply su to a new shell. (Lazy!)

== Using portupgrade and portversion ==

Now that that's done, you need to update your ports database.

<pre>oyabun# portsdb -Uu</pre>

This will likely take a while.

Now you can use [[portversion]] to see a list of installed programs that are out of date like so:

<pre>oyabun# portversion | grep '<'
expat <
ezm3 <
fontconfig <
freetype2 <
imake <
libnet-devel <
libtool <
oyabun#</pre>

This is a possible example of the output you'd recieve from portversion. Issuing a portversion command without the ''| grep '<''' would produce a list of ALL installed packages on your machine, with '''<''' for "out of date", '''=''' for "current", and '''>''' for "newer". How can you get "newer" than what's in the ports tree? I don't know exactly, but it will happen to you, and someone who reads this needs to explain it.

Now, to upgrade one of these packages, do this:

<pre>oyabun# portupgrade imake</pre>

Portupgrade will upgrade the port with the newer version available in the ports tree, and also take care of any dependencies the new version may have - if it needed ANOTHER installed port upgraded to a newer version, for example.

That's it. You'll have to repeat these steps (portversion, then portupgrade on one of the results) a few times to complete update your software, but all in all it's fairly simple and straightforward.

Note - you may sometimes be prompted to run '''pkgdb -F''' to fix inconsistencies with listed dependencies within programs when you issue portversion commands, after upgrading ports. Just do it (''oyabun# pkgdb -F'') and it will take care of the problem, allowing you to issue the portversion command.

Portupgrade

2004-08-25T03:56:09Z

Pete:

'''portupgrade and you'''

portupgrade is a small collection of tools that goes hand in hand with [[cvsup]]. Portupgrade does what it says - upgrades your ports - but it actually means your ''installed'' ports, even packages that were installed as part of the base system. Portupgrade includes two important programs - ''portupgrade'', and [[portversion]]. Between them and cvsup, you'll have the ability to keep all installed software on your system up to date, so long as it exists in the ports tree.

See also - [[cvsup]] - [[Update_the_ports_tree]] - [[portversion]]

== Installing the Portupgrade suite ==

Installation is very simple:

<pre>> su
Enter password:
oyabun# cd /usr/ports/sysutils/portupgrade
oyabun# make install clean</pre>

Once it's done, you'll have to ''exit and re-enter'' your session as [[superuser]] to use it without typing full pathnames. This assumes you used [[su]] to become root from a different account. If you logged in from the physical console as root, you can exit and re-login, or you can simply su to a new shell. (Lazy!)

== Using portupgrade and portversion ==

Now that that's done, you can use [[portversion]] to see a list of installed programs that are out of date like so:

<pre>oyabun# portversion | grep '<'
expat <
ezm3 <
fontconfig <
freetype2 <
imake <
libnet-devel <
libtool <
oyabun#</pre>

This is a possible example of the output you'd recieve from portversion. Issuing a portversion command without the ''| grep '<''' would produce a list of ALL installed packages on your machine, with '''<''' for "out of date", '''=''' for "current", and '''>''' for "newer". How can you get "newer" than what's in the ports tree? I don't know exactly, but it will happen to you, and someone who reads this needs to explain it.

Now, to upgrade one of these packages, do this:

<pre>oyabun# portupgrade imake</pre>

Portupgrade will upgrade the port with the newer version available in the ports tree, and also take care of any dependencies the new version may have - if it needed ANOTHER installed port upgraded to a newer version, for example.

That's it. You'll have to repeat these steps (portversion, then portupgrade on one of the results) a few times to complete update your software, but all in all it's fairly simple and straightforward.

Note - you may sometimes be prompted to run '''pkgdb -F''' to fix inconsistencies with listed dependencies within programs when you issue portversion commands, after upgrading ports. Just do it (''oyabun# pkgdb -F'') and it will take care of the problem, allowing you to issue the portversion command.

Portupgrade

2004-08-25T03:54:27Z

Pete:

'''portupgrade and you'''

portupgrade is a small collection of tools that goes hand in hand with [[cvsup]]. Portupgrade does what it says - upgrades your ports - but it actually means your ''installed'' ports, even packages that were installed as part of the base system. Portupgrade includes two important programs - ''portupgrade'', and [[portversion]]. Between them and cvsup, you'll have the ability to keep all installed software on your system up to date, so long as it exists in the ports tree.

See also - [[cvsup]] - [[Update_the_ports_tree]] - [[portversion]]

== Installing the Portupgrade suite ==

Installation is very simple:

<pre>> su
Enter password:
oyabun# cd /usr/ports/sysutils/portupgrade
oyabun# make install clean</pre>

Once it's done, you'll have to ''exit and re-enter'' your session as [[superuser]] to use it without typing full pathnames. This assumes you used [[su]] to become root from a different account. If you logged in from the physical console as root, you can exit and re-login, or you can simply su to a new shell. (Lazy!)

Now that that's done, you can use [[portversion]] to see a list of installed programs that are out of date like so:

<pre>oyabun# portversion | grep '<'
expat <
ezm3 <
fontconfig <
freetype2 <
imake <
libnet-devel <
libtool <
oyabun#</pre>

This is a possible example of the output you'd recieve from portversion. Issuing a portversion command without the ''| grep '<''' would produce a list of ALL installed packages on your machine, with '''<''' for "out of date", '''=''' for "current", and '''>''' for "newer". How can you get "newer" than what's in the ports tree? I don't know exactly, but it will happen to you, and someone who reads this needs to explain it.

Now, to upgrade one of these packages, do this:

<pre>oyabun# portupgrade imake</pre>

Portupgrade will upgrade the port with the newer version available in the ports tree, and also take care of any dependencies the new version may have - if it needed ANOTHER installed port upgraded to a newer version, for example.

That's it. You'll have to repeat these steps (portversion, then portupgrade on one of the results) a few times to complete update your software, but all in all it's fairly simple and straightforward.

Note - you may sometimes be prompted to run '''pkgdb -F''' to fix inconsistencies with listed dependencies within programs when you issue portversion commands, after upgrading ports. Just do it (''oyabun# pkgdb -F'') and it will take care of the problem, allowing you to issue the portversion command.

Portupgrade

2004-08-25T03:40:41Z

Pete:

Portupgrade

2004-08-25T03:33:30Z

Pete:

placeholder

Ports Tree, Updating

2004-08-25T03:24:18Z

Pete: /* It's updated. Now what? */

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 apporpriate for you and go into that directory and "make install clean":

dave@samizdata:~% su -
Password:
samizdata# cd /usr/ports/net/
samizdata# ls cvsup*
cvsup:
Makefile distinfo pkg-descr.nogui scripts
README.html pkg-descr pkg-plist

cvsup-mirror:
Makefile files pkg-descr pkg-plist
README.html pkg-deinstall pkg-install scripts

cvsup-without-gui:
Makefile README.html

cvsupit:
Makefile pkg-descr pkg-plist
README.html pkg-install pkg-req

samizdata# cd cvsup-without-gui/
samizdata# ls
Makefile README.html
samizdata# make install clean

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/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]] 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.

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

cvsup -g -L2 /root/ports-supfile

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]]

[[Category:Common Tasks]]

User:Dave

2004-08-25T03:12:53Z

Pete:

I do some unix, linux and BSD stuff for a university in South Florida.

I also do the stingray ho. Life is good.

User:Pete

2004-08-25T03:12:02Z

Pete:

STAY OUT OF MY MIND!!!111

Apache2, Installing

2004-08-24T16:09:22Z

Pete:

'''Apache 2.0'''

See also [[Apache]] - [[Apache2_Configuration]]

We'll walk through the installation for Apache2. It's very simple to install - in earlier versions of Apache, you had to install either mods or different versions depending on whether you wanted to enable certain features (ssl, etc). With Apache2, they are incorporated into the main package, and enabled or disabled when you configure Apache. There are a few exceptions, but most everything you'll need to run a modern feature-rich webserver is included with the Apache2 port.

'''Note:''' As always, before installing any ports, update your ports tree with [[CVSUP]] if it has been a while.

Let's get started:

<pre>>su
Password: (enter root password)
oyabun# cd /usr/ports/www
oyabun# ls | grep apache

apache-contrib
apache-forrest
apache-jserv
apache13
apache13+ipv6
apache13-fp
apache13-modperl
apache13-modssl
apache13-modssl+ipv6
apache13-ssl

apache2

mod_jk-apache2
mod_jk2-apache2

oyabun# cd apache2
oyabun# make install clean</pre>

First, I changed to the [[superuser]], as we'll be installing software. I changed directory to the '''www''' section of the ports tree, and filtered a listing of that directories contents for all ports that contained the word 'apache' using [[grep]]. The one we want is '''apache2'''. I then changed to that directory, and issued the [[make]] command, with options '''install''' and '''clean''' specified, to install the software and clean up the makefiles when done.

After a seconds, minutes, or hours, depending on whether your hardware is going to waste, reasonable, or a throwback to the early 90's, Apache2's installation will be completed, and you'll be faced with this note:

<pre>Available variables you add/set to /etc/rc.conf.
- apache2_enable (bool): Set to "NO" by default.
Set it to "YES" to enable apache2.
- apache2ssl_enable (bool): Set to "NO" by default.
Set it to "YES" to start apache with SSL
(if <IfDefined SSL> exists in httpd.conf).
- apache2limits_enable (bool):Set to "NO" by default.
Set it to yes to run `limits $limits_args`
just before apache starts.
- apache2_flags (str): Set to "" by default.
Extra flags passed to start command.
- apache2limits_args (str): Default to "-e -C daemon"
Arguments of pre-start limits run.</pre>

As you can see from this, ssl suport is included in Apache2, as opposed to Apache 1.3. I included this output because I have a bad habit of scrolling important stuff like this out of the buffer after installations, and it's nice to have it saved here. You don't need to worry about any of this until you configure Apache.

So, Apache2 is now installed, you just need to actually set it up.

Please visit [[Apache2_Configuration]] to actually configure and start your webserver.

Apache

2004-08-24T16:01:44Z

Pete:

[[Apache]] is an (some would say ''the'') open source webserver; used more than any other webserver in the world. It is available for easy installation from FreeBSD's [[:Category:Ports|ports tree]] in several different flavors, including pre-configured versions with and without [[OpenSSL]], [[mod_php]], [[frontpage extensions]], and lots more.

For most purposes, Apache is absolutely the only webserver worth considering. In very high-volume (or tiny-hardware) contexts that need absolute maximum hardware efficiency at the expense of flexibility and configurability, however, you may wish to consider [[thttpd]], which is designed for absolute bare-bones simplicity for the delivery of static (no CGI, no SSI, no PHP, no nothing) HTML.

See also - [[Apache2_Installation]] - [[Apache2_Configuration]]

[[Category:Ports and Packages]]

Apache

2004-08-24T16:01:23Z

Pete:

Apache

2004-08-24T16:01:05Z

Pete:

[[Apache]] is an (some would say ''the'') open source webserver; used more than any other webserver in the world. It is available for easy installation from FreeBSD's [[:Category:Ports|ports tree]] in several different flavors, including pre-configured versions with and without [[OpenSSL]], [[mod_php]], [[frontpage extensions]], and lots more.

For most purposes, Apache is absolutely the only webserver worth considering. In very high-volume (or tiny-hardware) contexts that need absolute maximum hardware efficiency at the expense of flexibility and configurability, however, you may wish to consider [[thttpd]], which is designed for absolute bare-bones simplicity for the delivery of static (no CGI, no SSI, no PHP, no nothing) HTML.

See also - [[Apache2]] - [[Apache2_Installation]]

[[Category:Ports and Packages]]

Apache2, Installing

2004-08-24T16:00:04Z

Pete:

'''Apache 2.0'''

See also [[Apache]] - [[Apache2_Configuration]]

We'll walk through the installation for Apache2. It's very simple to install - in earlier versions of Apache, you had to install either mods or different versions depending on whether you wanted to enable certain features (ssl, etc). With Apache2, they are incorporated into the main package, and enabled or disabled when you configure Apache. There are a few exceptions, but most everything you'll need to run a modern feature-rich webserver is included with the Apache2 port.

'''Note:''' As always, before installing any ports, update your ports tree with [[CVSUP]] if it has been a while.

Let's get started:

<pre>>su
Password: (enter root password)
oyabun# cd /usr/ports/www
oyabun# ls | grep apache

apache-contrib
apache-forrest
apache-jserv
apache13
apache13+ipv6
apache13-fp
apache13-modperl
apache13-modssl
apache13-modssl+ipv6
apache13-ssl

apache2

mod_jk-apache2
mod_jk2-apache2

oyabun# cd apache2
oyabun# make install clean</pre>

First, I changed to the [[superuser]], as we'll be installing software. I changed directory to the '''www''' section of the ports tree, and filtered a listing of that directories contents for all ports that contained the word 'apache' using [[grep]]. The one we want is '''apache2'''. I then changed to that directory, and issued the [[make]] command, with options '''install''' and '''clean''' specified, to install the software and clean up the makefiles when done.

After a seconds, minutes, or hours, depending on whether your hardware is going to waste, reasonable, or a throwback to the early 90's, Apache2's installation will be completed, and you'll be faced with this note:

<pre>Available variables you add/set to /etc/rc.conf.
- apache2_enable (bool): Set to "NO" by default.
Set it to "YES" to enable apache2.
- apache2ssl_enable (bool): Set to "NO" by default.
Set it to "YES" to start apache with SSL
(if <IfDefined SSL> exists in httpd.conf).
- apache2limits_enable (bool):Set to "NO" by default.
Set it to yes to run `limits $limits_args`
just before apache starts.
- apache2_flags (str): Set to "" by default.
Extra flags passed to start command.
- apache2limits_args (str): Default to "-e -C daemon"
Arguments of pre-start limits run.</pre>

As you can see from this, ssl suport is included in Apache2, as opposed to Apache 1.3.

So, Apache2 is now installed, you just need to actually set it up.

Please visit [[Apache2_Configuration]] to actually configure and start your webserver.

Samba, Configuration

2004-08-24T03:16:42Z

Pete:

Samba - Simple Configuration

See also: [[Samba]] - [[Samba_Installation]]

This article will walk you through a quick setup of Samba - creating directories to be shared, telling Samba to share those directories, how to limit access to different shares, and finally, how to set up a windows machine to have unfettered access to appropriate shares based on the currently logged in user. This article assumes you have a fresh, unconfigured install ([[Samba_Installation]]) of Samba to work with.

== Setting up your shares on the machine ==

First we need to decide what we're going to share, or at the very least, where the shares will actually reside. The simplest way to do this is to simply create a new directory in an easy to remember place, say, '''/usr'''. You can either share that new folder directly, or create several new directories within it, and limit access to each directory based on criteria I will make clear later in this article. For now, let's assume you have two sets of documents, public and private, and that you want to limit users' access to those documents based on who they are - they can either access both, or just public. So:

<pre>Oyabun# mkdir /usr/smbroot
Oyabun# mkdir /usr/smbroot/public
Oyabun# mkdir /usr/smbroot/private</pre>

The first command creates the '''/usr/smbroot/''' directory, which will hold all of your shares. The second command creates the public directory, which '''all''' users will be able to access, and the third command creates the private directory, which only '''select''' users will be able to access.

Now we need to set [[permissions]] on these directories. The [[permissions]] article goes into great detail about permissions, but a quick run through here will be fine. We'll use [[chown]] to change ownership of these two directories now. We'll assume you have or will set up two groups for your users, one group named '''public''', and another named '''private'''.

<pre>Oyabun# chown :public /usr/smbroot/public
Oyabun# chown :private /usr/smbroot/private</pre>

The first command sets the owning group of /usr/smbroot/public to :public. The second command assigns ownership of /usr/smbroot/private to the group :private.

Now we need to set the actual [[permissions]] with [[chmod]].

<pre>Oyabun# chmod 770 /usr/smbroot/public
Oyabun# chmod 770 /usr/smbroot/private</pre>

Same [[permissions]] for each directory, broken down thusly: The first '''7''' is the 'owner' flag, and 7 means read/write/execute. The owner can do all of those things. The second '''7''' is the group flag, meaning the owning :group can also r/w/x. The third character, '''0''', is in the 'rest of the world' position, meaning anyone who is NOT the owner, and NOT a member of the owning group. They can't read, they can't write, and they can't execute. Since we're not setting up anonymous access, we don't want users who aren't explicitly defined as having access to actually have any access, and this will accomplish that.

== Configuring Samba to use your shares and interface with local Win.X machines ==

Ok, now we have the shares set up appropriately, we just need to define them for Samba. In '''/usr/local/etc/''', there is a file named "'''smb.conf.default'''". This is a seriously large and complex file with waaaay more options than the average user will ever need to get Samba up and running. I highly suggest you go through it, as it has several examples of methods used to share directories, and access restriction methods. For this article, we'll be writing an [[smb.conf]] from scratch.

'''[global]'''

The first section of your new [[smb.conf]] file should look like this:

<pre>[global]
workgroup = WORKGROUP
server string = NameOfServer
log file = /var/log/log.%m
max log size = 50
security = user
encrypt passwords = yes
socket options = TCP_NODELAY
preferred master = yes
</pre>

'''[global]''' is a header in the file, telling Samba all entries after that, before the next [section] are to be globally applied.

'''workgroup = WORKGROUP''' - Specifies which Windows Workgroup to make the server a member of.

'''server string = NameOfServer''' - Names the server. This is the name you'll see in network neighborhood. For example, my smb.conf names my server 'Oyabun'. (cuz it's the boss!)

'''log file = /var/log/log%m''' - Tells Samba to create log files for each machine that connects in the var/log/ directory. For example, if a machine with the name of ''johndesktop'' connected, a log file named '''log.johndesktop''' would be created in /var/log, and appropriate entries for that machine would be made there.

'''max log size = 50''': limits the size of each log files to x kilobytes, in this case 50. This is so you don't find a gig of logs a year down the road.

'''security = user''': This is '''important''', and integral to simple networking between your new Samba server and your Windows machines.

'''ecrypt passwords = yes''': This is also '''important''' - passwords must be encrypted for each machine to successfuly negotiate login credentials with your Samba server.

'''socket options = TCP_NODELAY''': This is not required, but the Samba documentation within smb.conf.default suggests this may yield better performance, so I include it.

'''preferred master = yes''': Windows machines "elect" master browsers, which is a machine which takes on the duties of describing to other machines what all the machine names and locations are. Since your Samba machine is likely to be the sanest machine on your network, it's a good idea to have it 'fudge' the election results and always be the master browser. This option causes Samba to force a browser election when it starts up, and cheats to give it a higher chance of 'winning'.

And that's the global section. Now, on to actually setting up shares.

----

'''[homes]'''

If you want your users to be able to access the home directories of their FreeBSD user accounts, add a [homes] section. If you do NOT want individual users to have private storage areas, do not include this section.

<pre>[homes]
comment = Home Directories
browseable = no
writeable = yes</pre>

The mere existence of [homes] tells Samba to allow users to have access to their home directories via network sharing. If it's not there, they don't have it.

'''comment = Home Directories''' is a description for the [section], and will show up in Windows Explorer under the 'comment' field.

'''browseable = no''' means users other than the owner can't see or browse the share. (I can't see your home directory, you can't see mine, but we're both valid users.) Similar in purpose and execution to the 'My Documents' folder Windows users are familiar with. Each user has their own 'My Documents' folder.

'''writeable = yes''' means users can save files in their home directories from across the network.

That's it, setting up home directories is simple.

---

'''[public]'''

Now we'll set up the publicly accessible folder, located at '''/usr/smbroot/public/'''.

<pre>[public]
comment = Public
path = /usr/smbroot/public
public = no
writeable = yes
write list = @public
directory mask = 0770
create mask = 0007</pre>

'''[public]''': "Create a new share named 'Public', which will look like a folder named 'Public' in Network Neighborhood.

'''comment = Public''': Same deal, this fills the 'comment' field in windows explorer / network neighborhood, when you're looking at the share.

'''path = /usr/smbroot/public''': This tells samba exactly where on the local machine to store files for this share. This is pretty important.

'''public = no''': This is sort of counter-intuitive, but you don't want this set to yes.

'''writeable = yes''': This tells Samba to let authorized users write to the directory.

'''write list = @public''': Lists the ''users'' and ''@groups'' allowed to write here. This is important! To define this further, or add more users or @groups, you'd write the line like this:
"valid users = joe bill @public @friends @dogs".

'''directory mask = 0007''': This causes directories created by network users to have permissions of 770, and anyone can delete them. To make only the owner and root@sambaserver have permission to remove them, change this to 1007. The last three digits of the mask '007' in this case, are '''subtracted''' from permissions of 777, digit by digit. So, 777 - 007 = 770.

'''create mask = 0007''': Same deal, only this applies to files. Again, set it to '1007' to only allow the owner and root@sambaserver permission to delete the file.

That's it - you've defined all the important parts of the share for Samba, so it knows where to find it, and how to limit users' access to it.

Test your new config with [[testparm]], which is a Samba tool that lets you validate your smb.conf.

<pre>Oyabun# testparm</pre>

I won't list the results here, but you should see a list of your shares. If there are any warnings or error messages, you'll want to analyze and correct the problem. Lastly, testparm will dump your smb.conf to the console.

---

'''[private]'''

Now we'll set up the private share. It will actually look just like the public share, with a few small changes.

<pre>[private]
comment = Private
path = /usr/smbroot/private
public = no
writeable = yes
valid users = @private
write list = @private
directory mask = 0770
create mask = 0007</pre>

Obviously we defined the basic stuff like [private] and where the directory is.

'''valid users = @private''' - This prevents anyone who is not a member of @private from having access to this share. Because '''public = no''', people who are NOT members of @private won't even see this share when they browse the server.

That's it, you now have two distinct shares set up, with two distinct sets of criteria to determine who gets access to those shares from a windows machine.

== User accounts in BSD, Samba, and Windows ==

There are two parts to this step, adding matching matching user accounts to the Samba server and the various windows machines, and adding matching Samba passwords to the Samba server for each user. '''Usernames and passwords must match exactly between the client Windows machines and the Samba server.'''

Let's say ''Bob'' logs onto his windows machine with the username "''bob''" and the password "''syeruncle''". He already has an existing windows account, obviously, so you don't need to set that up, but if he didn't, you would. Bob is going to be a member of the @public group.

The quickest way to do this is to use '''/stand/sysinstall''' to add the user. You can also add users via the command line with [[adduser]]. Make sure you make each user a member of the appropriate group!

''bob'' will be a member of @public
''greg'' will be a member of @private

Now we need to use [[smbpasswd]] to validate these users in the eyes of Samba.

Make sure you are root before doing the following:

<pre>Oyabun# su bob
Oyabun# smbpasswd
New SMB password:
Retype new SMB password:
Password changed for user bob.
Oyabun# exit</pre>

In this example, as root, I switched to bob, then used the [[smbpasswd]] command to define my Samba password. It asked me to enter a password, asked me to confirm it, then accounced that the password was changed. Then I typed '''exit''' to exit the shell-as-bob, return to my root shell.

Repeat this process for ''greg'', entering greg's password.

---

Finally, we're done. We have shares set up, user accounts are in place, and everything is ready to go - now we just have to start Samba. This is easy. A startup script was placed in "'''/usr/local/etc/rc.d/'''", with a likely name of "''samba.sh.default''".

Let's rename it, and run it.

<pre>Oyabun# cd /usr/local/etc/rc.d
Oyabun# mv samba.sh.default samba.sh
Oyabun# /usr/local/etc/rc.d/samba start
SambaOyabun#
Oyabun#</pre>

First, rename the file from samba.sh.default to samba.sh. Then, execute it, using the full path (it will complain otherwise). If all went well, after execting ''samba.sh start'', you'll see ''Samba'' inserted before the name of your server at the next shell prompt. This means Samba is indeed running, and that you can now attempt to connect to this machine from your Windows machines. You should do so, testing the various accounts you have set up to make sure they can all connect.

Congrats, you now have a Samba server.
[[Category:Common Tasks]]

Samba, Configuration

2004-08-24T02:47:55Z

Pete:

Samba - Simple Configuration

See also: [[Samba]] - [[Samba_Installation]]

This article will walk you through a quick setup of Samba - creating directories to be shared, telling Samba to share those directories, how to limit access to different shares, and finally, how to set up a windows machine to have unfettered access to appropriate shares based on the currently logged in user. This article assumes you have a fresh, unconfigured install ([[Samba_Installation]]) of Samba to work with.

== Setting up your shares on the machine ==

First we need to decide what we're going to share, or at the very least, where the shares will actually reside. The simplest way to do this is to simply create a new directory in an easy to remember place, say, '''/usr'''. You can either share that new folder directly, or create several new directories within it, and limit access to each directory based on criteria I will make clear later in this article. For now, let's assume you have two sets of documents, public and private, and that you want to limit users' access to those documents based on who they are - they can either access both, or just public. So:

<pre>Oyabun# mkdir /usr/smbroot
Oyabun# mkdir /usr/smbroot/public
Oyabun# mkdir /usr/smbroot/private</pre>

The first command creates the '''/usr/smbroot/''' directory, which will hold all of your shares. The second command creates the public directory, which '''all''' users will be able to access, and the third command creates the private directory, which only '''select''' users will be able to access.

Now we need to set [[permissions]] on these directories. The [[permissions]] article goes into great detail about permissions, but a quick run through here will be fine. We'll use [[chown]] to change ownership of these two directories now. We'll assume you have or will set up two groups for your users, one group named '''public''', and another named '''private'''.

<pre>Oyabun# chown :public /usr/smbroot/public
Oyabun# chown :private /usr/smbroot/private</pre>

The first command sets the owning group of /usr/smbroot/public to :public. The second command assigns ownership of /usr/smbroot/private to the group :private.

Now we need to set the actual [[permissions]] with [[chmod]].

<pre>Oyabun# chmod 770 /usr/smbroot/public
Oyabun# chmod 770 /usr/smbroot/private</pre>

Same [[permissions]] for each directory, broken down thusly: The first '''7''' is the 'owner' flag, and 7 means read/write/execute. The owner can do all of those things. The second '''7''' is the group flag, meaning the owning :group can also r/w/x. The third character, '''0''', is in the 'rest of the world' position, meaning anyone who is NOT the owner, and NOT a member of the owning group. They can't read, they can't write, and they can't execute. Since we're not setting up anonymous access, we don't want users who aren't explicitly defined as having access to actually have any access, and this will accomplish that.

== Configuring Samba to use your shares and interface with local Win.X machines ==

Ok, now we have the shares set up appropriately, we just need to define them for Samba. In '''/usr/local/etc/''', there is a file named "'''smb.conf.default'''". This is a seriously large and complex file with waaaay more options than the average user will ever need to get Samba up and running. I highly suggest you go through it, as it has several examples of methods used to share directories, and access restriction methods. For this article, we'll be writing an [[smb.conf]] from scratch.

'''[global]'''

The first section of your new [[smb.conf]] file should look like this:

<pre>[global]
workgroup = WORKGROUP
server string = NameOfServer
log file = /var/log/log.%m
max log size = 50
security = user
encrypt passwords = yes
socket options = TCP_NODELAY
preferred master = yes
</pre>

'''[global]''' is a header in the file, telling Samba all entries after that, before the next [section] are to be globally applied.

'''workgroup = WORKGROUP''' - Specifies which Windows Workgroup to make the server a member of.

'''server string = NameOfServer''' - Names the server. This is the name you'll see in network neighborhood. For example, my smb.conf names my server 'Oyabun'. (cuz it's the boss!)

'''log file = /var/log/log%m''' - Tells Samba to create log files for each machine that connects in the var/log/ directory. For example, if a machine with the name of ''johndesktop'' connected, a log file named '''log.johndesktop''' would be created in /var/log, and appropriate entries for that machine would be made there.

Second line: limits the size of each log files to x kilobytes, in this case 50. This is so you don't find a gig of logs a year down the road.

'''security = user''': This is '''important''', and integral to simple networking between your new Samba server and your Windows machines.

'''ecrypt passwords = yes''': This is also '''important''' - passwords must be encrypted for each machine to successfuly negotiate login credentials with your Samba server.

'''socket options = TCP_NODELAY''': This is not required, but the Samba documentation within smb.conf.default suggests this may yield better performance, so I include it.

'''preferred master = yes''': Windows machines "elect" master browsers, which is a machine which takes on the duties of describing to other machines what all the machine names and locations are. Since your Samba machine is likely to be the sanest machine on your network, it's a good idea to have it 'fudge' the election results and always be the master browser. This option causes Samba to force a browser election when it starts up, and cheats to give it a higher chance of 'winning'.

And that's the global section. Now, on to actually setting up shares.

----

'''[homes]'''

If you want your users to be able to access the home directories of their FreeBSD user accounts, add a [homes] section. If you do NOT want individual users to have private storage areas, do not include this section.

<pre>[homes]
comment = Home Directories
browseable = no
writeable = yes</pre>

The mere existence of [homes] tells Samba to allow users to have access to their home directories via network sharing. If it's not there, they don't have it.

'''comment = Home Directories''' is a description for the [section], and will show up in Windows Explorer under the 'comment' field.

'''browseable = no''' means users other than the owner can't see or browse the share. (I can't see your home directory, you can't see mine, but we're both valid users.) Similar in purpose and execution to the 'My Documents' folder Windows users are familiar with. Each user has their own 'My Documents' folder.

'''writeable = yes''' means users can save files in their home directories from across the network.

That's it, setting up home directories is simple.

---

'''[public]'''

Now we'll set up the publicly accessible folder, located at '''/usr/smbroot/public/'''.

<pre>[public]
comment = Public
path = /usr/smbroot/public
public = no
writeable = yes
write list = @public
directory mask = 0770
create mask = 0007</pre>

'''[public]''': "Create a new share named 'Public', which will look like a folder named 'Public' in Network Neighborhood.

'''comment = Public''': Same deal, this fills the 'comment' field in windows explorer / network neighborhood, when you're looking at the share.

'''path = /usr/smbroot/public''': This tells samba exactly where on the local machine to store files for this share. This is pretty important.

'''public = no''': This is sort of counter-intuitive, but you don't want this set to yes.

'''writeable = yes''': This tells Samba to let authorized users write to the directory.

'''write list = @public''': Lists the ''users'' and ''@groups'' allowed to write here. This is important! To define this further, or add more users or @groups, you'd write the line like this:
"valid users = joe bill @public @friends @dogs".

'''directory mask = 0007''': This causes directories created by network users to have permissions of 770, and anyone can delete them. To make only the owner and root@sambaserver have permission to remove them, change this to 1007. The last three digits of the mask '007' in this case, are '''subtracted''' from permissions of 777, digit by digit. So, 777 - 007 = 770.

'''create mask = 0007''': Same deal, only this applies to files. Again, set it to '1007' to only allow the owner and root@sambaserver permission to delete the file.

That's it - you've defined all the important parts of the share for Samba, so it knows where to find it, and how to limit users' access to it.

---

'''[private]'''

Now we'll set up the private share. It will actually look just like the public share, with a few small changes.

<pre>[private]
comment = Private
path = /usr/smbroot/private
public = no
writeable = yes
valid users = @private
write list = @private
directory mask = 0770
create mask = 0007</pre>

Obviously we defined the basic stuff like [private] and where the directory is.

'''valid users = @private''' - This prevents anyone who is not a member of @private from having access to this share. Because '''public = no''', people who are NOT members of @private won't even see this share when they browse the server.

== User accounts and permissions in BSD and Samba ==

== Configuring a Windows machine with matching settings ==

Ideally, you want the user account and password on a windows machine attempting to make a connection to have a matching user account and password on the Samba server. In fact, if it's a Win9x machine, it's a '''requirement'''. Windows 2000 and XP will both challenge the user to supply proper credentials if their username and password don't match any that Samba and BSD recognize as valid, but Windows 95 and 98 both will simply not work - it's imperative that a matching user account exist on the Samba server.

[[Category:Common Tasks]]

Samba, Configuration

2004-08-24T02:34:38Z

Pete:

Samba - Simple Configuration

See also: [[Samba]] - [[Samba_Installation]]

This article will walk you through a quick setup of Samba - creating directories to be shared, telling Samba to share those directories, how to limit access to different shares, and finally, how to set up a windows machine to have unfettered access to appropriate shares based on the currently logged in user. This article assumes you have a fresh, unconfigured install ([[Samba_Installation]]) of Samba to work with.

== Setting up your shares on the machine ==

First we need to decide what we're going to share, or at the very least, where the shares will actually reside. The simplest way to do this is to simply create a new directory in an easy to remember place, say, '''/usr'''. You can either share that new folder directly, or create several new directories within it, and limit access to each directory based on criteria I will make clear later in this article. For now, let's assume you have two sets of documents, public and private, and that you want to limit users' access to those documents based on who they are - they can either access both, or just public. So:

<pre>Oyabun# mkdir /usr/smbroot
Oyabun# mkdir /usr/smbroot/public
Oyabun# mkdir /usr/smbroot/private</pre>

The first command creates the '''/usr/smbroot/''' directory, which will hold all of your shares. The second command creates the public directory, which '''all''' users will be able to access, and the third command creates the private directory, which only '''select''' users will be able to access.

Now we need to set [[permissions]] on these directories. The [[permissions]] article goes into great detail about permissions, but a quick run through here will be fine. We'll use [[chown]] to change ownership of these two directories now. We'll assume you have or will set up two groups for your users, one group named '''public''', and another named '''private'''.

<pre>Oyabun# chown :public /usr/smbroot/public
Oyabun# chown :private /usr/smbroot/private</pre>

The first command sets the owning group of /usr/smbroot/public to :public. The second command assigns ownership of /usr/smbroot/private to the group :private.

Now we need to set the actual [[permissions]] with [[chmod]].

<pre>Oyabun# chmod 770 /usr/smbroot/public
Oyabun# chmod 770 /usr/smbroot/private</pre>

Same [[permissions]] for each directory, broken down thusly: The first '''7''' is the 'owner' flag, and 7 means read/write/execute. The owner can do all of those things. The second '''7''' is the group flag, meaning the owning :group can also r/w/x. The third character, '''0''', is in the 'rest of the world' position, meaning anyone who is NOT the owner, and NOT a member of the owning group. They can't read, they can't write, and they can't execute. Since we're not setting up anonymous access, we don't want users who aren't explicitly defined as having access to actually have any access, and this will accomplish that.

== Configuring Samba to use your shares and interface with local Win.X machines ==

Ok, now we have the shares set up appropriately, we just need to define them for Samba. In '''/usr/local/etc/''', there is a file named "'''smb.conf.default'''". This is a seriously large and complex file with waaaay more options than the average user will ever need to get Samba up and running. I highly suggest you go through it, as it has several examples of methods used to share directories, and access restriction methods. For this article, we'll be writing an [[smb.conf]] from scratch.

'''[global]'''

The first section of your new [[smb.conf]] file should look like this:

<pre>[global]
log file = /var/log/log.%m
max log size = 50
security = user
encrypt passwords = yes
socket options = TCP_NODELAY
preferred master = yes
</pre>

'''[global]''' is a header in the file, telling Samba all entries after that, before the next [section] are to be globally applied.

The first line tells Samba to create log files for each machine that connects in the var/log/ directory. For example, if a machine with the name of ''johndesktop'' connected, a log file named '''log.johndesktop''' would be created in /var/log, and appropriate entries for that machine would be made there.

Second line: limits the size of each log files to x kilobytes, in this case 50. This is so you don't find a gig of logs a year down the road.

'''security = user''': This is '''important''', and integral to simple networking between your new Samba server and your Windows machines.

'''ecrypt passwords = yes''': This is also '''important''' - passwords must be encrypted for each machine to successfuly negotiate login credentials with your Samba server.

'''socket options = TCP_NODELAY''': This is not required, but the Samba documentation within smb.conf.default suggests this may yield better performance, so I include it.

'''preferred master = yes''': Windows machines "elect" master browsers, which is a machine which takes on the duties of describing to other machines what all the machine names and locations are. Since your Samba machine is likely to be the sanest machine on your network, it's a good idea to have it 'fudge' the election results and always be the master browser. This option causes Samba to force a browser election when it starts up, and cheats to give it a higher chance of 'winning'.

And that's the global section. Now, on to actually setting up shares.

----

'''[homes]'''

If you want your users to be able to access the home directories of their FreeBSD user accounts, add a [homes] section. If you do NOT want individual users to have private storage areas, do not include this section.

<pre>[homes]
comment = Home Directories
browseable = no
writeable = yes</pre>

The mere existence of [homes] tells Samba to allow users to have access to their home directories via network sharing. If it's not there, they don't have it.

'''comment = Home Directories''' is a description for the [section], and will show up in Windows Explorer under the 'comment' field.

'''browseable = no''' means users other than the owner can't see or browse the share. (I can't see your home directory, you can't see mine, but we're both valid users.) Similar in purpose and execution to the 'My Documents' folder Windows users are familiar with. Each user has their own 'My Documents' folder.

'''writeable = yes''' means users can save files in their home directories from across the network.

That's it, setting up home directories is simple.

---

'''[public]'''

Now we'll set up the publicly accessible folder, located at '''/usr/smbroot/public/'''.

<pre>[public]
comment = Public
path = /usr/smbroot/public
public = no
writeable = yes
write list = @public
directory mask = 0770
create mask = 0007</pre>

'''[public]''': "Create a new share named 'Public', which will look like a folder named 'Public' in Network Neighborhood.

'''comment = Public''': Same deal, this fills the 'comment' field in windows explorer / network neighborhood, when you're looking at the share.

'''path = /usr/smbroot/public''': This tells samba exactly where on the local machine to store files for this share. This is pretty important.

'''public = no''': This is sort of counter-intuitive, but you don't want this set to yes.

'''writeable = yes''': This tells Samba to let authorized users write to the directory.

'''write list = @public''': Lists the ''users'' and ''@groups'' allowed to write here. This is important! To define this further, or add more users or @groups, you'd write the line like this:
"valid users = joe bill @public @friends @dogs".

'''directory mask = 0007''': This causes directories created by network users to have permissions of 770, and anyone can delete them. To make only the owner and root@sambaserver have permission to remove them, change this to 1007. The last three digits of the mask '007' in this case, are '''subtracted''' from permissions of 777, digit by digit. So, 777 - 007 = 770.

'''create mask = 0007''': Same deal, only this applies to files. Again, set it to '1007' to only allow the owner and root@sambaserver permission to delete the file.

== User accounts and permissions in BSD and Samba ==

== Configuring a Windows machine with matching settings ==

Ideally, you want the user account and password on a windows machine attempting to make a connection to have a matching user account and password on the Samba server. In fact, if it's a Win9x machine, it's a '''requirement'''. Windows 2000 and XP will both challenge the user to supply proper credentials if their username and password don't match any that Samba and BSD recognize as valid, but Windows 95 and 98 both will simply not work - it's imperative that a matching user account exist on the Samba server.

File:Samba Installation installmenu.png

2004-08-24T00:48:09Z

Pete:

Samba, Installation

2004-08-23T20:33:17Z

Pete:

Installing Samba under FreeBSD is simple and painless. The easiest method is to install from ports, which also guarantees you'll get the latest released version. Be sure to use [[CVSUP]] to update your ports tree before installing any software.

See also: [[Samba]] - [[Samba_Configuration]]

All operations listed in this article must be performed by the [[superuser]], so [[su]] to root.

This install procedure will walk you through a basic, simple Samba install. No printers, no complicated options, just samba with some extended logging options which you don't even have to ever look at to run or use samba.

First, find the port:
<pre>oyabun# cd /usr/ports/net
oyabun# ls | grep samba
gnosamba
py-samba
samba
samba-devel
samba-libsmbclient
samba3
sambasentinel
oyabun#</pre>

This lists all samba-related ports in the net category. We want the '''samba''' port.

<pre>oyabun# cd samba</pre>
[[Category:Common Tasks]]

Now, we need to install it.

<pre>oyabun# make install clean</pre>

This will start the installation process, downloading and compiling the necessary files. It will '''install''' it (after it asks some questions) and then it will '''clean''' all the work files after it's done.

Shortly, you'll see a menu, which you should configure thusly:

[[Image:Samba_Installation_installmenu.png]]

'''With syslog''' will enable some logging to the syslog, as well as Samba's internal logs. '''Without CUPS''' means you don't want to configure print services right now, you just want Samba to share your files.

Make sure both of those options are selected (by moving the arrows keys and selecting them with space) then hit enter. Samba will now be installed, and barring accidents or problems, you will eventually be dumped back to a shell# prompt.

That's it. You just installed Samba. Now you need to configure it ( [[Samba_Configuration]] ), but you're done with step one.

User talk:Dave

2004-08-23T20:28:19Z

Pete:

HI A/S/L

User talk:Dave

2004-08-23T20:27:55Z

Pete:

HOMO

Samba, Installation

2004-08-23T20:26:26Z

Pete:

Installing Samba under FreeBSD is simple and painless. The easiest method is to install from ports, which also guarantees you'll get the latest released version. Be sure to use [[CVSUP]] to update your ports tree before installing any software.

See also: [[Samba]] - [[Samba_Configuration]]

All operations listed in this article must be performed by the superuser, so su to root.

This install procedure will walk you through a basic, simple Samba install. No printers, no complicated options, just samba with some extended logging options which you don't even have to ever look at to run or use samba.

First, find the port:
<pre>oyabun# cd /usr/ports/net
oyabun# ls | grep samba
gnosamba
py-samba
samba
samba-devel
samba-libsmbclient
samba3
sambasentinel
oyabun#</pre>

This lists all samba-related ports in the net category. We want the '''samba''' port.

<pre>oyabun# cd samba</pre>
[[Category:Common Tasks]]

Now, we need to install it.

<pre>oyabun# make install clean</pre>

This will start the installation process, downloading and compiling the necessary files. It will '''install''' it (after it asks some questions) and then it will '''clean''' all the work files after it's done.

Shortly, you'll see a menu, which you should configure thusly:

[[Image:Samba_Installation_installmenu.png]]

'''With syslog''' will enable some logging to the syslog, as well as Samba's internal logs. '''Without CUPS''' means you don't want to configure print services right now, you just want Samba to share your files.

Make sure both of those options are selected (by moving the arrows keys and selecting them with space) then hit enter. Samba will now be installed, and barring accidents or problems, you will eventually be dumped back to a shell# prompt.

That's it. You just installed Samba. Now you need to configure it ( [[Samba_Configuration]] ), but you're done with step one.

Samba, Installation

2004-08-23T20:26:02Z

Pete:

Installing Samba under FreeBSD is simple and painless. The easiest method is to install from ports, which also guarantees you'll get the latest released version. Be sure to use [[CVSUP]] to update your ports tree before installing any software.

See also: [[Samba]] - [[Samba_Configuration]]

All operations listed in this article must be performed by the superuser, so su to root.

This install procedure will walk you through a basic, simple Samba install. No printers, no complicated options, just samba with some extended logging options which you don't even have to ever look at to run or use samba.

First, find the port:
<pre>oyabun# cd /usr/ports/net
oyabun# ls | grep samba
gnosamba
py-samba
samba
samba-devel
samba-libsmbclient
samba3
sambasentinel
oyabun#</pre>

This lists all samba-related ports in the net category. We want the '''samba''' port.

<pre>oyabun# cd samba</pre>
[[Category:Ports]]

Now, we need to install it.

<pre>oyabun# make install clean</pre>

This will start the installation process, downloading and compiling the necessary files. It will '''install''' it (after it asks some questions) and then it will '''clean''' all the work files after it's done.

Shortly, you'll see a menu, which you should configure thusly:

[[Image:Samba_Installation_installmenu.png]]

'''With syslog''' will enable some logging to the syslog, as well as Samba's internal logs. '''Without CUPS''' means you don't want to configure print services right now, you just want Samba to share your files.

Make sure both of those options are selected (by moving the arrows keys and selecting them with space) then hit enter. Samba will now be installed, and barring accidents or problems, you will eventually be dumped back to a shell# prompt.

That's it. You just installed Samba. Now you need to configure it ( [[Samba_Configuration]] ), but you're done with step one.

Samba

2004-08-23T20:25:35Z

Pete:

Samba ([http://www.samba.org samba.org]) is an open-source program that, in a nutshell, makes FreeBSD (or any flavor of Unix it has been ported to) look and act like a Windows machine from the perspective of REAL windows machines.

This means Samba can be used to set up network shares (file and printer) that Win.x machines on the same network can access, just as if the FreeBSD machine was an actual Windows server.

This main page will be updated as articles are added, and will act as a portal to the rest of the Samba-related content on this wiki.

These articles will cover installing Samba under FreeBSD, configuring it, and configuring the client windows machines.

[[Samba_Installation]] -
[[Samba_Configuration]]
[[Category:Ports]]