Browsing Dakota translation

38.

This example uses <filename>/srv/samba/sharename</filename> because, according to the <emphasis>Filesystem Hierarchy Standard (FHS)</emphasis>, <ulink url="http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM"> /srv</ulink> is where site-specific data should be served. Technically, <application>Samba</application> shares can be placed anywhere on the filesystem as long as the permissions are correct, but adhering to standards is recommended.

39.

<emphasis>browsable:</emphasis> enables <trademark class="registered">Windows</trademark> clients to browse the shared directory using <application>Windows Explorer</application>.

40.

<emphasis>guest ok:</emphasis> allows clients to connect to the share without supplying a password.

41.

<emphasis>read only:</emphasis> determines if the share is read only or if write privileges are granted. Write privileges are allowed only when the value is <emphasis>no</emphasis>, as is seen in this example. If the value is <emphasis>yes</emphasis>, then access to the share is read only.

42.

<emphasis>create mask:</emphasis> determines the permissions new files will have when created.

43.

Now that <application>Samba</application> is configured, the directory needs to be created and the permissions changed. From a terminal, enter:

44.

sudo mkdir -p /srv/samba/share

45.

sudo chown nobody.nogroup /srv/samba/share/

46.

The <emphasis>-p</emphasis> switch tells <command>mkdir</command> to create the entire directory tree if it doesn't exist. Change the share name to fit the environment.

47.

Finally, restart the <application>samba</application> services to enable the new configuration: