|
|
27.
|
|
|
That's all there is to it. <application>Samba</application> is ready to be configured for file sharing.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:99(para)
|
|
|
29.
|
|
|
The main <application>Samba</application> configuration file is located in <filename>/etc/samba/smb.conf</filename>. The default configuration file has a significant number of comments in order to document various configuration directives.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:107(para)
|
|
|
30.
|
|
|
Not all of the available options are included in the default configuration file. See the <filename>smb.conf</filename><application>man</application> page or the <ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/"><application>Samba</application> HOWTO Collection</ulink> for more details.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:136(para)
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:194(para)
|
|
|
39.
|
|
|
<emphasis>browsable:</emphasis> enables <trademark class="registered">Windows</trademark> clients to browse the shared directory using <application>Windows Explorer</application>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:206(para)
|
|
|
43.
|
|
|
Now that <application>Samba</application> is configured, the directory needs to be created and the permissions changed. From a terminal, enter:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:203(para)
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:212(para)
|
|
|
50.
|
|
|
From a <trademark class="registered">Windows</trademark> client, it should now be possible to browse to the <phrase>Kubuntu</phrase> file server and see the shared directory. To check that everything is working, try creating a directory from <trademark class="registered">Windows</trademark>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:278(para)
|
|
|
58.
|
|
|
There are two security levels available to the Common Internet Filesystem (<acronym>CIFS</acronym>) network protocol <emphasis>user-level</emphasis> and <emphasis>share-level</emphasis>. <application>Samba</application>'s <emphasis>security mode</emphasis> implementation allows more flexibility, providing four ways of implementing user-level security and one way to implement share-level:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:327(para)
|
|
|
59.
|
|
|
<emphasis>security = user:</emphasis> requires clients to supply a username and password to connect to shares. <application>Samba</application> user accounts are separate from system accounts, but the <application>libpam-smbpass</application> package will sync system users and passwords with the <application>Samba</application> user database.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:289(para)
|
