Thứ Bảy, 15 tháng 2, 2014
Tài liệu Using Samba-2. Installing Samba on a Unix System-P1 pptx
libreadline.so.3 => /usr/lib/libreadline.so.3
libdl.so.2 => /lib/libdl.so.2
libcrypt.so.1 => /lib/libcrypt.so.1
libc.so.6 => /lib/libc.so.6
libtermcap.so.2 => /lib/libtermcap.so.2
/lib/ld-linux.so.2 => /lib/ld-linux.so.2
• If there are any incompatibilities between Samba and specific libraries
on your machine, the distribution-specific documentation should
highlight those.
• Keep in mind that each binary distribution carries preset values about
the target platform, such as default directories and configuration
option values. Again, check the documentation and the makefile
included in the source directory to see which directives and variables
were used when the binary was compiled. In some cases, these will
not be appropriate for your situation.
A few configuration items can be reset with command-line options at
runtime instead of at compile time. For example, if your binary tries to
place any log, lock, or status files in the "wrong" place (for example,
in /usr/local ), you can override this without recompiling.
One point worth mentioning is that the Samba source requires an ANSI C
compiler. If you are on a platform with a non-ANSI compiler, such as the cc
compiler on SunOS version 4, you'll have to install an ANSI-compliant
compiler such as gcc before you do anything else.[ 3
] If installing a compiler
isn't something you want to wrestle with, you can start off with a binary
package. However, for the most flexibility and compatibility on your system,
we always recommend compiling from the latest source.
[3] gcc binaries are available for almost every modern machine. See
http://www.gnu.org/
for a list of sites with gcc and other GNU software.
2.1.2 Read the Documentation
This sounds like an obvious thing to say, but there have probably been times
where you have uncompressed a package, blindly typed configure,
make, and make install, and walked away to get another cup of coffee.
We'll be the first to admit that we do that, many more times than we should.
It's a bad idea - especially when planning a network with Samba.
Samba 2.0 automatically configures itself prior to compilation. This reduces
the likelihood of a machine-specific problem, but there may be an option
mentioned in the README file that you end up wishing for after Samba's
been installed. With both source and binary packages you'll find a large
number of documents in the docs directory, in a variety of formats. The most
important files to look at in the distribution are:
WHATSNEW.txt
docs/textdocs/UNIX_INSTALL.txt
These files tell you what features you can expect in your Samba distribution,
and will highlight common installation problems that you're likely to face.
Be sure to look over both of them before you start the compilation process.
2.2 Configuring Samba
The source distribution of Samba 2.0 and above doesn't initially have a
makefile. Instead, one is generated through a GNU configure script, which is
located in the samba-2.0.x /source/ directory. The configure script, which
must be run as root, takes care of the machine-specific issues of building
Samba. However, you still may want to decide on some global options.
Global options can be set by passing options on the command-line:
# ./configure with-ssl
For example, this will configure the Samba makefile with support for the
Secure Sockets Layer (SSL) encryption protocol. If you would like a
complete list of options, type the following:
#./configure help
Each of these options enable or disable various features. You typically
enable a feature by specifying the with- feature option, which will
cause the feature to be compiled and installed. Likewise, if you specify a
without- feature option, the feature will be disabled. As of Samba
2.0.5, each of the following features is disabled by default:
with-smbwrapper
Include SMB wrapper support, which allows executables on the Unix
side to access SMB/CIFS filesystems as if they were regular Unix
filesystems. We recommend using this option. However, at this time
this book went to press, there were several incompatibilities between
the smbwrapper package and the GNU libc version 2.1, and it would
not compile on Red Hat 6.0. Look for more information on these
incompatibilities on the Samba home page.
with-afs
Include support of the Andrew Filesystem from Carnegie Mellon
University. If you're going to serve AFS files via Samba, we
recommend compiling Samba once first without enabling this feature
to ensure that everything runs smoothly. Once that version is working
smoothly, recompile Samba with this feature enabled and compare
any errors you might receive against the previous setup.
with-dfs
Include support for DFS, a later version of AFS, used by OSF/1
(Digital Unix). Note that this is not the same as Microsoft DFS, which
is an entirely different filesystem. Again, we recommend compiling
Samba once first without this feature to ensure that everything runs
smoothly, then recompile with this feature to compare any errors
against the previous setup.
with-krb4= base-directory
Include support for Kerberos version 4.0, explicitly specifying the
base directory of the distribution. Kerberos is a network security
protocol from MIT that uses private key cryptography to provide
strong security between nodes. Incidentally, Microsoft has announced
that Kerberos 5.0 will be the standard authentication mechanism for
Microsoft Windows 2000 (NT 5.0). However, the Kerberos 5.0
authentication mechanisms are quite different from the Kerberos 4.0
security mechanisms. If you have Kerberos version 4 on your system,
the Samba team recommends that you upgrade and use the with-
krb5 option (see the next item). You can find more information on
Kerberos at http://web.mit.edu/kerberos/www.
with-krb5= base-directory
Include support for Kerberos version 5.0, explicitly specifying the
base directory of the distribution. Microsoft has announced that
Kerberos 5.0 will be the standard authentication mechanism for
Microsoft Windows 2000 (NT 5.0). However, there is no guarantee
that Microsoft will not extend Kerberos for their own needs in the
future. Currently, Samba's Kerberos support only uses a plaintext
password interface and not an encrypted one. You can find more
information on Kerberos at its home page:
http://web.mit.edu/kerberos/www.
with-automount
Include support for automounter, a feature often used on sites that
offer NFS.
with-smbmount
Include smbmount support, which is for Linux only. This feature
wasn't being maintained at the time the book was written, so the
Samba team made it an optional feature and provided smbwrapper
instead. The smbwrapper feature works on more Unix platforms than
smbmount, so you'll usually want to use with-smbwrapper
instead of this option.
with-pam
Include support for pluggable authentication modules (PAM), an
authentication feature common in the Linux operating system.
with-ldap
Include support for the Lightweight Directory Access Protocol
(LDAP). A future version of LDAP will be used in the Windows 2000
(NT 5.0) operating system; this Samba support is experimental. LDAP
is a flexible client-server directory protocol that can carry information
such as certificates and group memberships.[ 4
]
[4] By directory, we don't mean a directory in a file system, but
instead an indexed directory (such as a phone directory). Information
is stored and can be easily retrieved in a public LDAP system.
with-nis
Include support for getting password-file information from NIS
(network yellow pages).
with-nisplus
Include support for obtaining password-file information from NIS+,
the successor to NIS.
with-ssl
Include experimental support for the Secure Sockets Layer (SSL),
which is used to provide encrypted connections from client to server.
Appendix A, Configuring Samba with SSL, describes setting up
Samba with SSL support.
with-nisplus-home
Include support for locating which server contains a particular user's
home directory and telling the client to connect to it. Requires
with-nis and, usually, with-automounter.
with-mmap
Include experimental memory mapping code. This is not required for
fast locking, which already uses mmap or System V shared memory.
with-syslog
Include support for using the SYSLOG utility for logging information
generated from the Samba server. There are a couple of Samba
configuration options that you can use to enable SYSLOG support;
Chapter 4, Disk Shares , discusses these options.
with-netatalk
Include experimental support for interoperating with the (Macintosh)
Netatalk file server.
with-quotas
Include disk-quota support.
Because each of these options is disabled by default, none of these features
are essential to Samba. However, you may want to come back and build a
modified version of Samba if you discover that you need one at a later time.
In addition, Table 2.1
shows some other parameters that you can give the
configure script if you wish to store parts of the Samba distribution in
different places, perhaps to make use of multiple disks or partitions. Note
that the defaults sometimes refer to a prefix specified earlier in the table.
Table 2.1: Additional Configure Options
Option Meaning Default
Table 2.1: Additional Configure Options
Option Meaning Default
prefix=
directory
Install architecture-independent
files at the base directory
specified.
/usr/local/samba
eprefix=
directory
Install architecture-dependent
files at the base directory
specified.
/usr/local/samba
bindir=
directory
Install user executables in the
directory specified.
eprefix /bin
sbindir=
directory
Install administrator executables
in the directory specified.
eprefix /bin
libexecdir=
directory
Install program executables in the
directory specified.
eprefix
/libexec
Table 2.1: Additional Configure Options
Option Meaning Default
datadir=
directory
Install read-only architecture
independent data in the directory
specified.
prefix /share
libdir=
directory
Install program libraries in the
directory specified.
eprefix /lib
includedir=
directory
Install package include files in
the directory specified.
prefix
/include
infodir=
directory
Install additional information
files in the directory specified.
prefix /info
mandir=
directory
Install manual pages in the
directory specified.
prefix /man
Again, before running the configure script, it is important that you are the
root user on the system. Otherwise, you may get a warning such as:
Đăng ký:
Đăng Nhận xét (Atom)
Không có nhận xét nào:
Đăng nhận xét