Adding initial copy of "Using Samba (3rd ed)"

docs-xml/using_samba/appe.xml

@@ -0,0 +1,46 @@
+<appendix label="E" id="SAMBA-AP-E">
+<title>Downloading Samba with CVS</title>
+
+
+
+
+<para>
+<indexterm id="appe-idx-992918-0"><primary>downloads</primary><secondary>Samba</secondary><tertiary sortas="obtainedusing CVS">obtained using CVS</tertiary></indexterm>
+<indexterm id="appe-idx-992918-1"><primary>Samba</primary><secondary>downloading</secondary><tertiary>with CVS</tertiary></indexterm>This appendix contains information on how to download the latest source version of Samba using the C<indexterm id="appe-idx-992919-0"><primary>Concurrent Versions System (CVS)</primary></indexterm>
+<indexterm id="appe-idx-992919-1"><primary>CVS (Concurrent Versions Systems)</primary></indexterm>oncurrent Versions System (CVS). CVS is a freely available configuration management tool available from <indexterm id="appe-idx-992920-0"><primary>Cyclic Software</primary></indexterm>Cyclic Software and is distributed under the<indexterm id="appe-idx-992921-0"><primary>GNU General Public License (GPL)</primary></indexterm> GNU General Public License. You can download the latest copy from <systemitem role="url">http://www.cyclic.com/</systemitem>.<indexterm id="appe-idx-992922-0"><primary>URLs (uniform resource locators)</primary><secondary>Cyclic Software</secondary></indexterm></para>
+
+
+<para>CVS works on top of the GNU <indexterm id="appe-idx-992923-0"><primary>Revision Control System
+(RCS)</primary></indexterm>
+<indexterm id="appe-idx-992923-1"><primary>RCS (Revision Control
+System)</primary></indexterm>Revision Control System (RCS). Many Unix
+systems come preinstalled with RCS. However, if you want to download
+the latest version of RCS, you can find it at <indexterm id="appe-idx-992936-0"><primary>URLs (uniform resource
+locators)</primary><secondary>RCS (Revision Control
+System)</secondary></indexterm><systemitem role="url">http://ftp.gnu.org/gnu/rcs/</systemitem>.</para>
+
+
+<para>One of the nicest things about CVS is its ability to handle remote logins. This means that people across the globe on the Internet can download and update various source files for any project that uses a CVS repository. Such is the case with Samba. Once you have RCS and CVS installed on your system, you must first log in to the Samba source server with the following command:</para>
+
+
+<programlisting>cvs -d :pserver:cvs@cvs.samba.org:/cvsroot login</programlisting>
+
+
+<para>This tells CVS to connect to the CVS server at <filename>cvs.samba.org</filename>. Once you are connected, you can download the latest source tree with the following command:</para>
+
+
+<programlisting>cvs -d :pserver:cvs@cvs.samba.org:/cvsroot co samba</programlisting>
+
+
+<para>This will download the entire Samba distribution (file by file) into a directory entitled <filename>/samba</filename>, which it will create on your hard drive. This directory will have the same structure as the Samba source distribution described in <link linkend="SAMBA-CH-2">Chapter 2</link>. It includes source and header files, documentation, and sample configuration files to help get you started. After that is completed, you can follow the instructions in <link linkend="SAMBA-CH-2">Chapter 2</link> to configure and compile Samba on your server.</para>
+
+
+
+
+
+
+
+
+
+
+</appendix>

docs-xml/using_samba/appf.xml

@@ -0,0 +1,250 @@
+<appendix label="F" id="SAMBA-AP-F">
+<title>Sample Configuration File</title>
+
+
+
+
+<para>
+<indexterm id="appf-idx-993481-0" class="startofrange"><primary>configuration files</primary><secondary>sample of</secondary></indexterm>This appendix gives an example of a production <filename>smb.conf</filename> file and looks at how many of the options are used in practice. The following is a slightly disguised version of one we used at a corporation with five Linux servers, five Windows for Workgroups clients and three NT Workstation clients:</para>
+
+
+<programlisting># smb.conf -- File Server System for: 1 Example.COM  BSC &amp; Management Office
+[globals]
+	workgroup = 1EG_BSC
+	interfaces = 10.10.1.14/24</programlisting>
+
+
+<para>We provide this service on only one of the machine's interfaces. The <literal>interfaces</literal> option sets its address and netmask, where <literal>/24</literal> is the same as using the netmask 255.255.255.0:</para>
+
+
+<programlisting>comment = Samba ver. %v
+	preexec = csh -c `echo /usr/samba/bin/smbclient \
+                     -M %m -I %I` &amp;</programlisting>
+
+
+<para>We use the <command>preexec</command> command to log information about all connections by machine name (<literal>%m</literal>) and IP address (<literal>%I)</literal>:</para>
+
+
+<programlisting># smbstatus will output various info on current status
+	status = yes
+	browseable = yes
+	printing = bsd
+
+	# the username that will be used for access to services
+	# specified with 'guest = ok'
+	guest account = samba</programlisting>
+
+
+<para>The default guest account was <literal>nobody</literal>, uid -1, which produced log messages on one of our machines saying "your server is being unfriendly," so we created a specific Samba guest account for browsing and printing:</para>
+
+
+<programlisting># superuser account - admin privilages to shares, with no
+	# restrictions
+	# WARNING - use this with care: files can be modified,
+	# regardless of file permissions
+	admin users = root
+
+	# who is NOT allowed to connect to ANY service
+	invalid users = @wheel, mail, deamon, adt</programlisting>
+
+
+<para>Daemons can't use Samba, only people. The <literal>invalid</literal> <literal>users</literal> option closes a security hole; it prevents intruders from breaking in by pretending to be a daemon process.</para>
+
+
+<programlisting># hosts that are ALLOWED or DENIED from connecting to ANY service
+	hosts allow = 10.10.1.
+	hosts deny = 10.10.1.6
+
+	# where the lock files will be located
+	lock directory = /var/lock/samba/locks
+
+	# debug log files
+	# %m = separate log for each NetBIOS name (each machine)
+	log file = /var/log/samba/log.%m
+
+	# We send priority 0, 1 and 2 messages to the system logs
+	syslog = 2
+
+	# If a WinPopup message is sent to the server,
+	# redirect it to a user via e-mail
+
+	message command = /bin/mail -s 'message from #% on %m' \
+                               pkelly &lt; %s; rm %s
+
+# ---------------------------------------------------
+# [globals] Performance Tuning
+# ---------------------------------------------------
+
+	# caching algorithm to reduce time doing getwd() calls.
+	getwd cache = yes
+
+	socket options = TCP_NODELAY
+
+	# tell the server whether the client is present and
+	# responding in seconds
+	keep alive = 60
+
+	# num minutes of inactivity before a connection is
+	# considered dead
+	dead time = 30
+
+	read prediction = yes
+	share modes = yes
+	max xmit = 17384
+	read size = 512</programlisting>
+
+
+<para>The <literal>share</literal> <literal>modes</literal>, <literal>max</literal>, <literal>xinit</literal>, and <literal>read</literal> <literal>size</literal> options are machine-specific (see <link linkend="SAMBA-AP-B">Appendix B</link>):</para>
+
+
+<programlisting># locking is done by the server
+	locking = yes
+
+	# control whether dos style attributes should be mapped
+	# to unix execute bits
+	map hidden = yes
+	map archive = yes
+	map system = yes</programlisting>
+
+
+<para>The three <literal>map</literal> options will work only on shares with a create mode that includes the execute bits (0111). Our <literal>homes</literal> and <literal>printers</literal> shares won't honor them, but the [<literal>www]</literal> share will:</para>
+
+
+<programlisting># ---------------------------------------------------------
+# [globals] Security and Domain Logon Services
+# ---------------------------------------------------------
+# connections are made with UID and GID, not as shares
+	security = user
+
+# boolean variable that controls whether passwords
+# will be encrypted
+	encrypt passwords = yes
+	passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"
+	passwd program = /usr/bin/passwd %u
+
+# Always become the local master browser
+	domain master = yes
+	preferred master = yes
+	os level = 34
+
+# For domain logons to work correctly. Samba acts as a
+# primary domain controller.
+	domain logons = yes
+
+# Logon script to run for user off the server each time
+# username (%U) logs in.  Set the time, connect to shares,
+# virus checks, etc.
+	logon script = scripts\%U.bat
+
+[netlogon]
+	comment = "Domain Logon Services"
+	path = /u/netlogon
+	writable = yes
+	create mode = 444
+	guest ok = no
+	volume = "Network"</programlisting>
+
+
+<para>This share, discussed in <link linkend="SAMBA-CH-6">Chapter 6</link>, is required for Samba to work smoothly in a Windows NT domain:</para>
+
+
+<programlisting># -----------------------------------------------------------
+# [homes] User Home Directories
+# -----------------------------------------------------------
+[homes]
+	comment = "Home Directory for : %u "
+	path = /u/users/%u</programlisting>
+
+
+<para>The password file of the Samba server specifies each person's home directory as   <emphasis>/home/</emphasis><replaceable>machine_name</replaceable><emphasis>/</emphasis><replaceable>person</replaceable>, which NFS converts to point to the actual physicl location under <emphasis>/u/users</emphasis>. The <literal>path</literal> option in the <literal>[homes]</literal> share tells Samba the actual (non-NFS) location:</para>
+
+
+<programlisting>guest ok = no
+	read only = no
+	create mode = 644
+	writable = yes
+	browseable = no
+
+# -----------------------------------------------------------
+# [printers] System Printers
+# -----------------------------------------------------------
+[printers]
+	comment = "Printers"
+	path = /var/spool/lpd/samba
+	printcap name = /etc/printcap
+	printable = yes
+	public = no
+	writable = no
+
+	lpq command = /usr/bin/lpq -P%p
+	lprm command = /usr/bin/lprm -P%p %j
+	lppause command = /usr/sbin/lpc stop %p
+	lpresume command = /usr/sbin/lpc start %p
+
+	create mode = 0700
+
+	browseable = no
+	load printers = yes
+
+# -----------------------------------------------------------
+# Specific Descriptions: [programs] [data] [retail]
+# -----------------------------------------------------------
+[programs]
+	comment = "Shared Programs %T"
+	volume = "programs"</programlisting>
+
+
+<para>Shared Programs shows up in the Network Neighborhood, and <literal>programs</literal> is the volume name you specify when an installation program wants to know the label of the CD-ROM from which it thinks it's loading:</para>
+
+
+<programlisting>path = /u/programs
+	public = yes
+	writeable = yes
+	printable = no
+	create mode = 664
+[cdrom]
+	comment = "Unix CDROM"
+	path = /u/cdrom
+	public = no
+	writeable = no
+	printable = no
+	volume = "cdrom"
+
+[data]
+	comment =  "Data Directories %T"
+	path = /u/data
+	public = no
+	create mode = 770
+	writeable = yes
+	volume = "data"
+
+[nt4]
+	comment =  "NT4 Server"
+	path = /u/systems/nt4
+	public = yes
+	create mode = 770
+	writeable = yes
+	volume = "nt4_server"
+
+[www]
+	comment =  "WWW System"
+	path = /usr/www/http
+	public = yes
+	create mode = 775
+	writeable = yes
+	volume = "www_system"</programlisting>
+
+
+<para>The <literal>[www]</literal> share is the directory used on the Unix server to serve web pages. Samba makes the directory available to local PC users so the art department can update web pages.</para>
+
+
+
+
+
+
+
+
+
+
+
+</appendix>

docs-xml/using_samba/book.xml

@@ -0,0 +1,51 @@
+<?xml version="1.0"?>
+<!DOCTYPE book PUBLIC
+"-//O'Reilly//DTD DBLite Safari 1.0 XML//EN"
+"/usr/local/prod/sgml/dblite/safari_future.dtd"
+[
+<!ENTITY metadata SYSTEM "metadata.xml">
+<!-- Declare external file entities -->
+<!ENTITY appa SYSTEM "appa.xml">
+<!ENTITY appb SYSTEM "appb.xml">
+<!ENTITY appc SYSTEM "appc.xml">
+<!ENTITY appd SYSTEM "appd.xml">
+<!ENTITY appe SYSTEM "appe.xml">
+<!ENTITY appf SYSTEM "appf.xml">
+<!ENTITY ch00 SYSTEM "ch00.xml">
+<!ENTITY ch01 SYSTEM "ch01.xml">
+<!ENTITY ch02 SYSTEM "ch02.xml">
+<!ENTITY ch03 SYSTEM "ch03.xml">
+<!ENTITY ch04 SYSTEM "ch04.xml">
+<!ENTITY ch05 SYSTEM "ch05.xml">
+<!ENTITY ch06 SYSTEM "ch06.xml">
+<!ENTITY ch07 SYSTEM "ch07.xml">
+<!ENTITY ch08 SYSTEM "ch08.xml">
+<!ENTITY ch09 SYSTEM "ch09.xml">
+<!ENTITY colo1 SYSTEM "colo1.xml">
+<!ENTITY cpyrt SYSTEM "copy.xml">
+]>
+<!-- Document type description -->
+<book fpi="1565924495">
+  <title>Using Samba</title>
+  <!-- Book metadata -->
+&metadata;
+<!-- Reference the file entities -->
+&cpyrt;
+&ch00;
+&ch01;
+&ch02;
+&ch03;
+&ch04;
+&ch05;
+&ch06;
+&ch07;
+&ch08;
+&ch09;
+&appa;
+&appb;
+&appc;
+&appd;
+&appe;
+&appf;
+&colo1;
+</book>

docs-xml/using_samba/ch00.xml

@@ -0,0 +1,330 @@
+<preface id="ch00">
+<title>Preface</title>
+
+
+
+
+<para>It's nine in the morning and you've just arrived at the computer center after a refreshing night's sleep. Your pager hasn't gone off in months. Life is pretty good as a system administrator &mdash; and why shouldn't it be, with the network you're running? Two hundred identical machines, all running the same operating system. All of the printers are networked, accessible from anywhere in the building, and the auto-configuration scripts that the manufacturer supplied ensure that everyone in the company has a consistent view of the shared disks you've set up. Yes, this is the good life. You lean back and take that first delicious sip of morning coffee . . . .</para>
+
+
+<para>And then, the alarm clock jolts you out of your blissful reverie. If you're like most system administrators, this could only be a dream. Your morning probably starts with a tireless struggle to get four different computer platforms running three different operating systems simply to talk to each other &mdash; that is, if the phone ever stops ringing. Most of your users don't understand why it's so hard to access a file on another computer or to send a job to a remote printer. The logs show that the backups are late. For some reason the PCs on the second floor can't find the tape server. With all these headaches, what's a network administrator to do?</para>
+
+
+<para>Easy: take the day off, read this book, and learn Samba!</para>
+
+
+
+
+
+
+
+
+
+
+
+<sect1 role="" id="ch00-SECT-1">
+<title>The Samba Suite</title>
+
+
+<para>Samba is a suite of tools for sharing resources such as printers and files across a network. This may be a bit of an oversimplification, but Samba is really designed to make your life easier. Samba uses the Server Message Block (SMB) protocol, which is endorsed jointly by Microsoft and IBM, to communicate low-level data between Windows clients and Unix servers on a TCP/IP network.</para>
+
+
+<para>
+<indexterm id="ch00-idx-941381-0"><primary>Samba</primary><secondary>features/uses</secondary></indexterm>Four features of Samba make it extremely attractive:</para>
+
+
+<itemizedlist>
+<listitem><para>Samba speaks the same SMB protocol that Microsoft and IBM operating systems have used as their standard since DOS 3.0. This means that almost all Windows machines already understand it and there is no extra client software to install.</para></listitem>
+<listitem><para>Samba runs on a variety of platforms, including most variants of Unix, OpenVMS, OS/2, AmigaDOS, and NetWare. This means that you can use a single program on the server to provide files and printers to a community of PCs.</para></listitem>
+<listitem><para>Samba is free. There are several commercial products that duplicate Samba's features, and some of them are quite expensive. Samba offers you an alternative to packages that could gobble up a significant portion of your IS budget. Samba is distributed under the GNU General Public License (GPL), and is considered by its authors to be <firstterm>Open Source</firstterm> software. In other words, you can freely download both the application and the accompanying source code to your computer, and even improve on the original Samba programs if you like.</para></listitem>
+<listitem><para>Samba administration is centralized on the server. You don't have to visit every one of your machines, floppy or CD-ROM in hand, to upgrade the client software.</para></listitem>
+</itemizedlist>
+
+<para>Samba is a complete solution for local area networks (LANs) of all sizes&mdash;everything from the two-computer home network to corporate installations with hundreds of nodes. Samba is simple to set up and to administer, and presents itself as a transparent network environment that offers users access to all of the resources they need to get their work done. Once you've set it up, Samba will let you:</para>
+
+
+<itemizedlist>
+<listitem><para>Serve Unix files to Windows, OS/2, and other OS clients</para></listitem>
+<listitem><para>Allow Unix clients to access PC files</para></listitem>
+<listitem><para>Serve network printers to Windows clients</para></listitem>
+<listitem><para>Provide name services (broadcast and WINS)</para></listitem>
+<listitem><para>Allow browsing of network resources from Windows clients</para></listitem>
+<listitem><para>Create Windows workgroups or domains</para></listitem>
+<listitem><para>Enforce username and password authentication of clients</para></listitem>
+</itemizedlist>
+</sect1>
+
+
+
+
+
+
+
+
+
+<sect1 role="" id="ch00-SECT-2">
+<title>Audience for this Book</title>
+
+
+<para>The primary audience of this book is Unix administrators who need to support PCs on their network, and anyone who needs to provide a Unix server in a PC environment. But we don't want to burden you with an endless series of arcane system administration tools and vocabulary. While we assume you are familiar with basic Unix system administration, we will <emphasis>not</emphasis> assume you are a networking expert. We'll do our best along the way to help out with unusual definitions and terms.</para>
+
+
+<para>Because we don't assume a tremendous amount of experience with Microsoft Windows, we will go through the PC side of the installation task in considerable detail and give examples for both Windows 95/98 and Windows NT, which are subtly different. For the Unix side, we will give examples for common Unix operating systems, such as Linux 2.0 or Solaris 2.6.</para>
+</sect1>
+
+
+
+
+
+
+
+
+
+<sect1 role="" id="ch00-SECT-3">
+<title>Samba Installation Checklist</title>
+
+
+<para>Before you get started, you should have:</para>
+
+
+<itemizedlist>
+<listitem><para><indexterm id="ch00-idx-941383-0"><primary>Samba</primary><secondary>version 2.0.5</secondary></indexterm><indexterm id="ch00-idx-941383-1"><primary>Samba</primary><secondary>distribution</secondary></indexterm><indexterm id="ch00-idx-941383-2"><primary>URLs (uniform resource locators)</primary><secondary>Samba</secondary><tertiary>distribution</tertiary></indexterm>
+
+<!-- CD-ROM REFERENCE COMMENTED OUT FOR SAFARI VERSION OF THIS TITLE.
+
+Either the CD-ROM from this book (which contains both source and binary distributions of Samba 2.0.5) or the latest Samba distribution, which you can download directly off the Internet at <systemitem role="url">http://www.samba.org/</systemitem>. </para>
+
+-->
+
+The latest Samba distribution, which you can download directly off the Internet at <systemitem role="url">http://www.samba.org/</systemitem>.</para></listitem>
+<listitem><para>The names and IP addresses of the servers and client machines you plan to use, the netmask of your network, and the names and IP addresses of your domain name (DNS) servers.</para></listitem>
+</itemizedlist>
+</sect1>
+
+
+
+
+
+
+
+
+
+<sect1 role="" id="ch00-SECT-4">
+<title>Organization</title>
+
+
+<para>The book can be roughly divided into two sections: Samba installation (<link linkend="ch01-48078">Chapter 1</link> through <link linkend="SAMBA-CH-3">Chapter 3</link>) and Samba configuration and optimization (<link linkend="ch04-21486">Chapter 4</link> through <link linkend="SAMBA-CH-9">Chapter 9</link>). Here is a detailed breakdown of each of the chapters:</para>
+
+
+<variablelist>
+<varlistentry><term><link linkend="ch01-48078">Chapter 1</link></term>
+<listitem><para>This chapter introduces each of the Samba components and gives a brief overview of NetBIOS and Windows networking.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-CH-2">Chapter 2</link></term>
+<listitem><para>This chapter covers configuring, compiling, installing, and testing the Samba server on a Unix platform.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-CH-3">Chapter 3</link></term>
+<listitem><para>This chapter explains how to configure Microsoft Windows 95/98 and NT 4.0 clients to participate in an SMB network. It also gives a brief introduction to the SMB protocol in action.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="ch04-21486">Chapter 4</link></term>
+<listitem><para>This chapter gets you up to speed with the individual parts of the Samba configuration file and shows you how to configure disk services.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-CH-5">Chapter 5</link></term>
+<listitem><para>This chapter continues the discussion of disk options and examines browsing with Samba.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-CH-6">Chapter 6</link></term>
+<listitem><para>This chapter discusses how to set up users, introduces you to Samba security, and shows you how to work with encrypted and non-encrypted passwords. We also discuss how to set up Samba as a primary domain controller for Windows 95/98 and NT clients.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-CH-7">Chapter 7</link></term>
+<listitem><para>This chapter discusses printer and Windows Internet Naming Service (WINS) setup with Samba.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-CH-8">Chapter 8</link></term>
+<listitem><para>This chapter bundles several miscellaneous activities associated with Samba, such as configuring Samba shares for programmers, internationalization issues, and backing up with <emphasis>smbtar</emphasis>.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-CH-9">Chapter 9</link></term>
+<listitem><para>If you have problems installing Samba, this comparatively large chapter is packed with troubleshooting hints and strategies as to what might be going wrong.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-AP-A">Appendix A</link></term>
+<listitem><para>This appendix shows you the nitty-gritty of setting up Samba with Secure Sockets Layers (SSL) connections between the server and its clients.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-AP-B">Appendix B</link></term>
+<listitem><para>This appendix discusses various techniques to optimize Samba processing on your network.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-AP-C">Appendix C</link></term>
+<listitem><para>This appendix covers each of the options used in the <filename>smb.conf</filename> file.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-AP-D">Appendix D</link></term>
+<listitem><para>Each of the server daemons and tools that make up the Samba suite are covered in this appendix. In addition, we provide a list of mirror sites on the Internet from which Samba can be downloaded.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-AP-E">Appendix E</link></term>
+<listitem><para>This appendix explains how to download the latest version of Samba with CVS.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><link linkend="SAMBA-AP-F">Appendix F</link></term>
+<listitem><para>This appendix provides a large-scale Samba configuration file, which you might find in place at a large corporation. We have embedded comments in the file to explain the more arcane options.</para></listitem>
+</varlistentry>
+</variablelist>
+</sect1>
+
+
+
+
+
+
+
+
+
+<sect1 role="" id="ch00-SECT-5">
+<title>Conventions</title>
+
+
+<para>The following font conventions are followed throughout this book:</para>
+
+
+<variablelist>
+<varlistentry><term>Italic </term>
+<listitem><para>Filenames, file extensions, URLs, Internet addresses, executable files, commands, and emphasis.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><literal>Constant Width</literal> </term>
+<listitem><para>Samba configuration options and other code that appear in the text, and command-line information that should be typed verbatim on the screen.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><userinput>Bold Constant Width</userinput> </term>
+<listitem><para>Commands that are entered by the user, and new configuration options that we wish to bring to the attention of the reader.</para></listitem>
+</varlistentry>
+
+
+<varlistentry><term><replaceable>Constant Width Italic</replaceable></term>
+<listitem><para>Replaceable content in code and command-line information.</para></listitem>
+</varlistentry>
+</variablelist>
+
+
+<tip id="ch00-NOTE-0" role="ora">
+<para>This icon designates a note, which is an important aside to the nearby text.</para>
+
+</tip>
+
+<warning id="ch00-NOTE-1" role="ora">
+<para>This icon designates a warning related to the nearby text.</para>
+
+</warning>
+</sect1>
+
+
+
+
+
+
+
+
+
+<sect1 role="" id="ch00-SECT-6">
+<title>Request for Comments</title>
+
+
+<para>As a reader of this book, you can help us to improve the next edition. If you find errors, inaccuracies, or typographical errors anywhere in the book, please let us at O'Reilly know about them. Also, if you find any misleading statements or confusing explanations, let us know that as well. Send all correspondence to:</para>
+
+
+<simplelist>
+
+<member>O'Reilly &amp; Associates</member>
+
+<member>101 Morris Street</member>
+
+<member>Sebastopol, CA 95472</member>
+
+<member>1-800-998-9938 (in the U.S. or Canada)</member>
+
+<member>1-707-829-0515 (international/local)</member>
+
+<member>1-707-829-0104 (fax)</member>
+
+<member><email>bookquestions@ora.com</email></member>
+
+</simplelist>
+
+
+<para>Please let us know what we can do to make the book more helpful to you. We take your comments seriously, and will do whatever we can to make this book as useful as it can be.</para>
+</sect1>
+
+
+
+
+
+
+
+
+
+<sect1 role="" id="ch00-SECT-7">
+<title>Acknowledgments</title>
+
+
+<para>Robert Eckstein</para>
+
+
+<blockquote>
+<para>I'd first like to recognize Dave Collier-Brown and Peter Kelly for all their help in the creation of this book. I'd also like to thank each of the technical reviewers that helped polish this book into shape on such short notice: Matthew Temple, Jeremy Allison, and of course Andrew Tridgell. Andrew and Jeremy deserve special recognition, not only for creating such a wonderful product, but for providing a tireless amount of support in the final phase of this book&mdash;hats off to you, guys! A warm hug goes out to my wife Michelle, who once again put up with a husband loaded down with too much caffeine on a tight schedule. Thanks to Dave Sifry and the people at LinuxCare, San Francisco, for hosting me on such short notice for Andrew Tridgell's visit. And finally, a huge amount of thanks to our editor, Andy Oram, who (very) patiently helped guide this book through its many stages until we got it right.</para>
+</blockquote>
+
+
+<para>David Collier-Brown</para>
+
+
+<blockquote>
+<para>I'd especially like to thank Joyce, who put up with me during the sometimes exciting development of the book. My thanks to Andy Oram, who was kind enough to provide the criticism that allowed me to contribute; the crew at Opcom who humored the obvious madman in their midst; and Ian MacMillan, who voluntarily translated several of my early drafts from nerd to English. I would also like to give special thanks to Perry Donham, Drew Sullivan, and Jerry DeRoo.</para>
+</blockquote>
+
+
+<para>Peter Kelly</para>
+
+
+<blockquote>
+<para>A few people really made this book possible, and I have to bow to them. Dave Collier-Brown, and then Bob Eckstein, took over my part of this project with style and professionalism and I can't explain how much I owe them for the great work that came out of it. Editor Andy Oram is by far the most patient and pleasant person I have met. Also, I don't think that I would have been involved in this book without the help of Xavier Cazin from O'Reilly, who originally came to me asking for a proposal after reading my Linux Journal article. I also would like to thank all of the JDP.COM consultants (  Jerry, Peggyann, Drew, Gord, Jerome, Mark, Rick&mdash;too many to list!) for allowing me to continue to work with them. I thank the O'Reilly staff that I have worked with as well; they are a great bunch of people. Also, thanks to the Samba Team for making Samba in the first place. And most importantly, Kate McKay, for staying with me this long!</para>
+</blockquote>
+
+
+<para>We would especially like to give thanks to Perry Donham for helping mold the first draft of this book. Although Perry was unable to contribute to subsequent drafts, his material was essential to getting this book off on the right foot. In addition, some of the browsing material came from text originally written by Dan Shearer for O'Reilly.</para>
+
+
+<para>We are deeply indebted to the production department at O'Reilly for another fantastic job. Sarah Jane Shangraw worked long hours accommodating our seemingly endless edits, and Rob Romano tirelessly edited our images again and again until they were perfect. Special thanks also to Claire Cloutier LeBlanc, Rhon Porter, and Mike Sierra for their help&mdash;we couldn't have done it without any of them. It is largely through their collective efforts that this book arrived to you in November 1999 instead of November 2000.</para>
+</sect1>
+
+
+
+
+
+
+
+
+</preface>

docs-xml/using_samba/colo1.xml

@@ -0,0 +1,67 @@
+<colophon id="colophon">
+<title>Colophon</title>
+
+
+
+
+<para>Our look is the result of reader comments, our own
+experimentation, and feedback from distribution channels. Distinctive
+covers complement our distinctive approach to technical topics,
+breathing personality and life into potentially dry subjects.</para>
+
+
+<para>The animal on the cover of <citetitle>Using Samba</citetitle> is
+a African ground hornbill (<foreignphrase>Bucorvus
+cafer</foreignphrase>). This type of bird is one of fifty hornbill
+species. The African ground hornbill is a medium to large sized bird
+characterized by a bright red waddle under a very long beak,
+dark-colored body and wings, long eyelashes, and short legs. Like all
+hornbills, it has a casque, a large but lightweight growth on the top
+of its beak, which grows more folds as the bird ages. It is the only
+ground-dwelling species of hornbill, though it is able to fly when
+necessary. It lives in the grasslands of southern and eastern Africa,
+and nests in the foliage of dense trees, not in nest holes in the
+ground as other hornbills do. Its diet includes mostly fruit, as well
+as large insects and small mammals. The African ground hornbill is
+considered to be sacred by many Africans, and as such this bird is
+part of many legends and superstitions.</para>
+
+
+<para>Sarah Jane Shangraw was the production editor and proofreader
+for <citetitle>Using Samba</citetitle>. Sarah Lemaire copyedited the
+text. Maureen Dempsey and Claire Cloutier LeBlanc provided quality
+control. Brenda Miller wrote the index.</para>
+
+
+<para>Edie Freedman designed the cover of this book based on her own
+series design. The cover image of an African ground hornbill is a
+19th-century engraving from the Dover Pictorial Archive. Kathleen
+Wilson produced the cover layout with QuarkXPress 3.32 using Adobe's
+ITC Garamond font. Kathleen Wilson also created the CD design.</para>
+
+
+<para>Alicia Cech designed the interior layout based on a series
+design by Nancy Priest. Mike Sierra implemented the design in
+FrameMaker 5.5. The text and heading fonts are ITC Garamond Light and
+Garamond Book. The illustrations that appear in the book were produced
+by Robert Romano and Rhon Porter using Macromedia FreeHand 8 and Adobe
+Photoshop 5. Interior composition was done by Sarah Jane Shangraw,
+Sebastian Banker, Jeff Holcolmb, and Abigail Myers. This colophon was
+written by Nicole Arigo.</para>
+
+
+
+
+
+
+
+
+
+
+
+<para>The online edition of this book was created by the Safari
+production group (John Chodacki, Becki Maisch, and Madeleine Newell)
+using a set of Frame-to-XML conversion and cleanup tools written and
+maintained by Erik Ray, Benn Salter, John Chodacki, and Jeff
+Liggett.</para>
+</colophon>

docs-xml/using_samba/copy.xml

@@ -0,0 +1,64 @@
+<preface id="copyright" role="copyrightpg">
+
+
+
+
+<para>Copyright &copy; 2000 O'Reilly &amp; Associates, Inc. All rights reserved. This material may be redistributed only under the terms of the Open Content
+License.  For information on the Open Content License under which the
+contents of this book are licensed, see <systemitem role="url">http://www.oreilly.com/catalog/samba/</systemitem>.</para>
+
+
+<para>Printed in the United States of America.</para>
+
+
+<para>Published by O'Reilly &amp; Associates, Inc., 101 Morris Street,
+Sebastopol, CA 95472.</para>
+
+
+
+
+
+
+
+
+
+
+
+
+
+<para>The O'Reilly logo is a registered trademark of O'Reilly &amp;
+Associates, Inc.  Many of the designations used by manufacturers and
+sellers to distinguish their products are claimed as trademarks.
+Where those designations appear in this book, and O'Reilly &amp;
+Associates, Inc. was aware of a trademark claim, the designations have
+been printed in caps or initial caps. The association between the
+image of the North African ground hornbill and the topic of Samba is
+a trademark of O'Reilly &amp; Associates, Inc.</para>
+
+
+
+
+
+
+
+
+
+
+
+
+
+<para>While every precaution has been taken in the preparation of this
+book, the publisher assumes no responsibility for errors or omissions,
+or for damages resulting from the use of the information contained
+herein.</para>
+
+
+
+
+
+
+
+
+
+
+</preface>