<authorgroup>\r
<author>&person.jht;</author>\r
</authorgroup>\r
- <pubdate>March 4, 2005</pubdate>\r
+ <pubdate>April 12, 2005</pubdate>\r
</bookinfo>\r
<?latex \clearpage ?>\r
-<!--- Leave the commented out lines they are needed for book production.\r
- <para>boo</para>\r
- <?latex \clearpage ?>\r
- <para>boo</para>\r
- <?latex \clearpage ?>\r
- <para>boo</para>\r
--->\r
+ <?latex \setcounter{page}{5} ?>\r
+\r
<xi:include href="inside-cover.xml"/>\r
<xi:include href="acknowledgements.xml"/>\r
<xi:include href="foreword.xml"/>\r
<xi:include href="preface.xml"/>\r
+\r
<?latex \cleardoublepage ?>\r
+\r
<toc/>\r
+\r
<?latex \cleardoublepage ?>\r
+\r
<?latex \listofexamples ?>\r
+\r
<?latex \cleardoublepage ?>\r
+\r
<lot/>\r
+\r
<!-- Chapters -->\r
- <xi:include href="Chap01-WindowsNetworkingPrimer.xml"/>\r
- <xi:include href="Chap02-SimpleOfficeServer.xml"/>\r
- <xi:include href="Chap03-TheSmallOffice.xml"/>\r
- <xi:include href="Chap04-SecureOfficeServer.xml"/>\r
- <xi:include href="Chap05-500UserNetwork.xml"/>\r
- <xi:include href="Chap06-MakingHappyUsers.xml"/>\r
- <xi:include href="Chap07-2000UserNetwork.xml"/>\r
- <xi:include href="Chap08-MigrateNT4Samba3.xml"/>\r
- <xi:include href="Chap08b-MigrateNW4Samba3.xml"/>\r
- <xi:include href="Chap09-AddingUNIXClients.xml"/>\r
- <xi:include href="Chap10-KerberosFastStart.xml"/>\r
- <xi:include href="Chap10b-DomainAppsSupport.xml"/>\r
- <xi:include href="Chap11-HighAvailability.xml"/>\r
- <xi:include href="Chap12-Appendix.xml"/>\r
+\r
+<part id="ExNetworks">\r
+<title>Example Network Configurations</title>\r
+<partintro>\r
+<title>Example Network Configurations</title>\r
+\r
+<?latex \pagenumbering{arabic} ?>\r
+\r
+<para>\r
+This section of <emphasis>Samba-3 by Example</emphasis> provides example network\r
+configurations that can be copied, or modified as needed, and deployed as-is.\r
+</para>\r
+\r
+<para>\r
+Best use can be made of this book by finding in this section the network design and\r
+layout that best approximates your estimated needs. It is recommended that you will\r
+implement the design pattern exactly as it appears, then after the installation has\r
+been proven to work make any changes or modifications needed at your site.\r
+</para>\r
+\r
+<para>\r
+The examples have been tested with Red Hat Fedora Core 2, Novell SUSE Linux Professional\r
+9.2 and Novell SUSE Linux Enterprise Server (SLES) 9. The principals of implementation\r
+apply to all Linux and UNIX systems in general, though some system files and tools will \r
+be different and the location of some Samba file locations will be different since these \r
+are determinered by the person who packages Samba for each platform.\r
+</para>\r
+\r
+</partintro>\r
+ <xi:include href="SBE-SimpleOfficeServer.xml"/>\r
+ <xi:include href="SBE-TheSmallOffice.xml"/>\r
+ <xi:include href="SBE-SecureOfficeServer.xml"/>\r
+ <xi:include href="SBE-500UserNetwork.xml"/>\r
+ <xi:include href="SBE-MakingHappyUsers.xml"/>\r
+ <xi:include href="SBE-2000UserNetwork.xml"/>\r
+</part>\r
+\r
+<part id="DMSMig">\r
+<title>Domain Membership and Migration</title>\r
+<partintro>\r
+<title>Domain Membership and Migration</title>\r
+\r
+<para>\r
+This section <emphasis>Samba-3 by Example</emphasis> covers two main topics: How to add\r
+Samba Domain Member Servers and Samba Domain Member Clients to a Samba domain, the other\r
+subject is that of how to migrate from and NT4 Domain, a NetWare server, or from an earlier\r
+Samba version to environments that use the most recent Samba-3 release. \r
+</para>\r
+\r
+<para>\r
+Those who are making use of the chapter on Adding UNIX clients and servers running Samba\r
+to a Samba or a Windows networking domain may also benefit by referring to the book\r
+<emphasis>The Official Samba-3 HOWTO and Reference Guide.</emphasis>\r
+</para>\r
+\r
+</partintro>\r
+ <xi:include href="SBE-AddingUNIXClients.xml"/>\r
+ <xi:include href="SBE-MigrateNT4Samba3.xml"/>\r
+ <xi:include href="SBE-MigrateNW4Samba3.xml"/>\r
+</part>\r
+\r
+<part id="RefSection">\r
+<title>Reference Section</title>\r
+<partintro>\r
+<title>Reference Section</title>\r
+\r
+<para>\r
+This section <emphasis>Samba-3 by Example</emphasis> provides important reference material\r
+that may help you to solve network performance issues, to answer some of the critiques\r
+published regarding Samba, or just to gain a more broad understanding of how Samba can\r
+play in a Windows networking world.\r
+</para>\r
+\r
+</partintro>\r
+ <xi:include href="SBE-KerberosFastStart.xml"/>\r
+ <xi:include href="SBE-DomainAppsSupport.xml"/>\r
+ <xi:include href="SBE-HighAvailability.xml"/>\r
+ <xi:include href="SBE-Appendix1.xml"/>\r
+ <xi:include href="SBE-Appendix2.xml"/>\r
<xi:include href="http://www.gnu.org/licenses/gpl.xml"/>\r
+</part>\r
<xi:include href="glossary.xml"/>\r
<index/>\r
</book>\r
</para>
<sect2>
- <title>Samba 3.0.12 Update Edition</title>
+ <title>Samba 3.0.15 Update Edition</title>
<para>
The Samba 3.0.x series has been remarkably popular. At the time this book first
</para>
<table id="pref-new">
- <title>Samba Changes &smbmdash; 3.0.2 to 3.0.12</title>
+ <title>Samba Changes &smbmdash; 3.0.2 to 3.0.15</title>
<tgroup cols="2">
<colspec align="left"/>
<colspec align="justify"/>
<title>Summary of Topics</title>
<para>
- Our first assignment is to understand how Microsoft Windows products
- function in the network environment. That is where we start. Let's take
- just a few moments to get a bird's eye view of this book. Remember that
- this is a book about file and print technology deployment; there are
- great examples of printing solutions. Here we go.
+ The contents of this second edition of <emphasis>Samba-3 by Example</emphasis>
+ have been rearranged based on feedback from purchasers of the first edition.
</para>
- <variablelist>
- <varlistentry>
- <term>Chapter 1 &smbmdash; Windows Networking Primer</term><listitem>
- <para>
- Here we cover practical exercises to help us to understand how MS Windows
- network protocols function. A network protocol analyzer helps you to
- appreciate the fact that Windows networking is highly dependent on broadcast
- messaging. Additionally, you can look into network packets that a Windows
- client sends to a network server to set up a network connection. On completion,
- you should have a basic understanding of how network browsing functions and
- have seen some of the information a Windows client sends to
- a file and print server to create a connection over which file and print
- operations may take place.
- </para>
- </listitem>
- </varlistentry>
+ <para>
+ Clearly the first edition contained most of what was needed and that was missing
+ from other books that cover this difficult subject. The new arrangement adds
+ additional material to meet consumer requests and includeis changes that originated
+ as suggestions for improvement.
+ </para>
+ <para>
+ Chapter 1 now dives directly into the heart of the implementation of Windows
+ file and print server networks that use Samba at the heart.
+ </para>
+
+ <variablelist>
<varlistentry>
- <term>Chapter 2 &smbmdash; No Frills Samba Servers</term><listitem>
+ <term>Chapter 1 &smbmdash; No Frills Samba Servers</term><listitem>
<para>
Here you design a solution for three different business scenarios, each for a
company called Abmas. There are two simple networking problems and one slightly
</varlistentry>
<varlistentry>
- <term>Chapter 3 &smbmdash; Small Office Networking</term><listitem>
+ <term>Chapter 2 &smbmdash; Small Office Networking</term><listitem>
<para>
Abmas is a successful company now. They have 50 network users
and want a little more varoom from the network. This is a typical
</varlistentry>
<varlistentry>
- <term>Chapter 4 &smbmdash; Secure Office Networking</term><listitem>
+ <term>Chapter 3 &smbmdash; Secure Office Networking</term><listitem>
<para>
Abmas is growing rapidly now. Money is a little tight, but with 130
network users, security has become a concern. They have many new machines
</varlistentry>
<varlistentry>
- <term>Chapter 5 &smbmdash; The 500 User Office</term><listitem>
+ <term>Chapter 4 &smbmdash; The 500 User Office</term><listitem>
<para>
The two-year projections were met. Congratulations, you are a star.
Now Abmas needs to replace the network. Into the existing user base, they
</varlistentry>
<varlistentry>
- <term>Chapter 6 &smbmdash; Making Users Happy</term><listitem>
+ <term>Chapter 5 &smbmdash; Making Users Happy</term><listitem>
<para>
Congratulations again. Abmas is happy with your services and you have been given another raise.
Your users are becoming much more capable and are complaining about little
</varlistentry>
<varlistentry>
- <term>Chapter 7 &smbmdash; A Distributed 2000-User Network</term><listitem>
+ <term>Chapter 6 &smbmdash; A Distributed 2000-User Network</term><listitem>
<para>
Only eight months have passed, and Abmas has acquired another company. You now need to expand
the network further. You have to deal with a network that spans several countries.
</varlistentry>
<varlistentry>
- <term>Chapter 8 &smbmdash; Migrating NT4 Domain to Samba-3</term><listitem>
+ <term>Chapter 7 &smbmdash; Migrating NT4 Domain to Samba-3</term><listitem>
<para>
Another six months have <?latex \linebreak ?>
passed. Abmas has acquired yet another company. You will find a
</varlistentry>
<varlistentry>
- <term>Chapter 9 &smbmdash; Migrating NetWare 4.11 Server to Samba</term><listitem>
+ <term>Chapter 8 &smbmdash; Migrating NetWare 4.11 Server to Samba</term><listitem>
<para>
Misty Stanley-Jones has contributed information that summarizes her experience at migration
from a NetWare server to Samba-3.
</varlistentry>
<varlistentry>
- <term>Chapter 10 &smbmdash; Adding UNIX/Linux Servers and Clients</term><listitem>
+ <term>Chapter 9 &smbmdash; Adding UNIX/Linux Servers and Clients</term><listitem>
<para>
Well done, Bob, your team has achieved much. Now help Abmas integrate the entire network.
You want central control and central support and you need to cut costs. How can you reduce administrative
</varlistentry>
<varlistentry>
- <term>Chapter 11 &smbmdash; Active Directory, Kerberos and Security</term><listitem>
+ <term>Chapter 10 &smbmdash; Active Directory, Kerberos and Security</term><listitem>
<para>
Abmas has acquired another company that has just migrated to running Windows Server 2003 and
Active Directory. One of your staff makes offhand comments that land you in hot water.
</varlistentry>
<varlistentry>
- <term>Chapter 12 &smbmdash; Integrating Additional Services</term><listitem>
+ <term>Chapter 11 &smbmdash; Integrating Additional Services</term><listitem>
<para>
The battle is almost over, Samba-3 has won the day. Your team are delighted and now you
find yourself at yet another cross-roads. Abmas have acquired a snack food business, you
</varlistentry>
<varlistentry>
- <term>Chapter 13 &smbmdash; Performance, Reliability and Availability</term><listitem>
+ <term>Chapter 12 &smbmdash; Performance, Reliability and Availability</term><listitem>
<para>
Bob, are you sure the new Samba server is up to the load? Your network is serving many
users who risk becoming unproductive. What can you do to keep ahead of demand? Can you
</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>Chapter 13 &smbmdash; Windows Networking Primer</term><listitem>
+ <para>
+ Here we cover practical exercises to help us to understand how MS Windows
+ network protocols function. A network protocol analyzer helps you to
+ appreciate the fact that Windows networking is highly dependent on broadcast
+ messaging. Additionally, you can look into network packets that a Windows
+ client sends to a network server to set up a network connection. On completion,
+ you should have a basic understanding of how network browsing functions and
+ have seen some of the information a Windows client sends to
+ a file and print server to create a connection over which file and print
+ operations may take place.
+ </para>
+ </listitem>
+ </varlistentry>
+
</variablelist>
</sect1>
git.samba.org / tprouty / samba.git / commitdiff