Currently the page says:
The installation commands installed a default configuration file which you can use as an example to set the values for your system and network. At a minimum, ensure you set the following value to an appropriate setting for your network in the /etc/samba/smb.conf configuration file:
workgroup = WORKGROUP
Also, for non-English locales, ensure the following values are set properly in the [global] section:
dos charset = cp850
unix charset = ISO-8859-1
The problems with this paragraph are stated in Comments #4 (important)
and #5 (minor) for
http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1386 (this bug is
NOT really fixed).
I suggest the following instead:
1) Move instructions under the heading "Printing to SMB Clients" above
"Configuring SAMBA".
2) Under "Configuration Information" use the following text or something
similar:
===================
The contents of /etc/samba/smb.conf depend on the purpose of SAMBA
installation.
Scenario 1: minimal standalone client-only installation. Choose this
variant if you only want to transfer files using smbclient, mount
Windows shares and print to Windows printers, and don't want to share
your files and printers to Windows machines.
The configuration file with the following three parameters is sufficient:
[global]
workgroup = MYGROUP
dos charset = cp850
unix charset = ISO-8859-1
The values in this example specify that the computer belongs to a
Windows workgroup named "MYGROUP", uses the cp850 character set on the
wire when talking to MS-DOS and MS Windows 9x, and that the filenames
are stored in the ISO-8859-1 encoding on the disk. Please adjust these
example values as appropriate to your site. "unix charset" must be the
same as the output of "locale charmap" with the LANG variable set to
your preferred locale, otherwise the "ls" command will not display
correct filenames of downloaded files.
There is no need to run any SAMBA servers in this scenario, thus you
don't need the provided bootscripts.
Scenario 2: Standalone file/print server. Choose this variant if you
want to share your files and printers to Windows machines in your
workgroup in addition to facilities described in Scenario 1.
In this case, the file examples/smb.conf.default in SAMBA source is a
good template to start from. Also add "dos charset" and "unix charset"
parameters to the [global] section as described in Scenario 1 in order
to prevent filename corruption. This configuration file creates a
separate share for each user's home directory and also makes all
printers available to Windows machines:
[global]
workgroup = MYGROUP
dos charset = cp850
unix charset = ISO-8859-1
[homes]
comment = Home Directories
browseable = no
writable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = no
printable = yes
Since the smbd and nmbd daemons are needed in this case, install the
samba bootscript. Be sure to run smbpasswd to enable and set passwords
for all accounts that need SAMBA access, or use SWAT web interface (see
below) to do the same.
<FIXME: expand the above paragraph a bit>
<FIXME: is the issue with kernel oplocks still relevant? I always
disable them.>
More complex scenarios involving domain control or membership are
possible if the right flags are passed to the ./configure script. Such
setups are advanced topics and cannot be adequately covered in BLFS. It
should be noted, however, that a Samba BDC cannot be used as a fallback
for a Windows PDC, and conversely, a Windows BDC cannot be used as a
fallback for a Samba PDC. Also in some domain mambership scenarios, the
winbindd daemon and the corresponding bootscript are needed.
There is quite a bit of documentation available which covers many of
these advanced configurations. Point your web browser to the links below
to view some of the documentation included with the Samba package:
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
