Updating version numbers.

(This used to be commit de92c975bae8cefb8840d1a44e82162243135aec)

8 files changed, 42 insertions, 41 deletions

diff --git a/docs/Samba-Guide/Chap01-WindowsNetworkingPrimer.xml b/docs/Samba-Guide/Chap01-WindowsNetworkingPrimer.xml
index bcbb8c4a36..dc35822cdb 100644
--- a/docs/Samba-Guide/Chap01-WindowsNetworkingPrimer.xml
+++ b/docs/Samba-Guide/Chap01-WindowsNetworkingPrimer.xml
@@ -204,15 +204,15 @@
 	</para>
 
 	<para>
-	For these exercises, our test environment consisted of a SUSE 8.2 Professional Linux Workstation running
-	VMWare 3.2. The following VMWare images were prepared:
+	For these exercises, our test environment consisted of a SUSE 9.2 Professional Linux Workstation running
+	VMWare 4.5. The following VMWare images were prepared:
 	</para>
 
 	<itemizedlist>
 		<listitem><para>Windows 98 &smbmdash; name: MILGATE98.</para></listitem>
 		<listitem><para>Windows Me &smbmdash; name: WINEPRESSME.</para></listitem>
 		<listitem><para>Windows XP Professional &smbmdash; name: LightrayXP.</para></listitem>
-		<listitem><para>Samba-3.0.2 running on a SUSE Enterprise Linux 8.0 machine.</para></listitem>
+		<listitem><para>Samba-3.0.12 running on a SUSE Enterprise Linux 9.</para></listitem>
 	</itemizedlist>
 
 	<para>
@@ -222,7 +222,7 @@
 	<para>
 	<indexterm><primary>ethereal</primary></indexterm>
 	The network captures provided on the CD-ROM at the back of this book were captured using <constant>ethereal</constant>
-	version <literal>0.9.10</literal>. A later version suffices without problems, but an earlier version may not
+	version <literal>0.10.6</literal>. A later version suffices without problems, but an earlier version may not
 	expose all the information needed. Each capture file has been decoded and listed as a trace file. A summary of all
 	packets has also been included. This makes it possible for you to do all the studying you like without the need to
 	perform the time-consuming equipment configuration and test work. This is a good time to point out the value
diff --git a/docs/Samba-Guide/Chap02-SimpleOfficeServer.xml b/docs/Samba-Guide/Chap02-SimpleOfficeServer.xml
index 8adc2ef78c..19ea7ef902 100644
--- a/docs/Samba-Guide/Chap02-SimpleOfficeServer.xml
+++ b/docs/Samba-Guide/Chap02-SimpleOfficeServer.xml
@@ -84,12 +84,13 @@
 	</para>
 
 	<para><indexterm>
-	    <primary>Red Hat Linux</primary>
+	    <primary>Red Hat</primary>
+	    <primary>Fedora</primary>
 	  </indexterm>
 	Mr. Bob Jordan has asked you to install the new server as economically as possible. The central
 	server has a Pentium-IV 1.6GHz CPU, 768MB RAM, a 20GB IDE boot drive, a 160GB IDE second disk
-	to store plans, and a 100-base-T Ethernet card. You have already installed Red Hat Linux 9.0 and
-	have upgraded Samba to version 3.0.2 using the RPM package that is provided from the Samba
+	to store plans, and a 100-base-T Ethernet card. You have already installed Red Hat Fedora Core2 and
+	have upgraded Samba to version 3.0.12 using the RPM package that is provided from the Samba
 	<ulink url="http://www.samba.org">FTP</ulink> sites.
 	</para>
 
@@ -144,7 +145,7 @@
 
 		<para>
 		It is assumed that the server is fully installed and ready for installation and 
-		configuration of Samba 3.0.2 and any support files needed. All TCP/IP addresses 
+		configuration of Samba 3.0.12 and any support files needed. All TCP/IP addresses 
 		have been hard coded. In our case the IP address of the Samba server is 
 		<constant>192.168.1.1</constant> and the netmask is <constant>255.255.255.0</constant>. 
 		The host name of the server used was <constant>server</constant>.
@@ -154,7 +155,7 @@
 		<title>Samba Server Configuration</title>
 
 			<step><para>
-			Download the Samba-3 RPM packages for Red Hat Linux 9.0 from the Samba
+			Download the Samba-3 RPM packages for Red Hat Fedora Core2 from the Samba
 			<ulink url="http://www.samba.org">FTP servers.</ulink>
 			</para></step>
 
@@ -167,7 +168,7 @@
 			Install the RPM package as using either the Red Hat Linux preferred GUI
 			tool or using the <command>rpm</command>, as follows:
 <screen>
-&rootprompt; rpm -Uvh samba-3.0.2-1.i386.rpm
+&rootprompt; rpm -Uvh samba-3.0.12-1.i386.rpm
 </screen>
 			</para></step>
 
@@ -297,12 +298,12 @@
         Sharename     Type     Comment
         ---------     ----     -------
         Plans         Disk
-        IPC$          IPC      IPC Service (Samba 3.0.2)
-        ADMIN$        IPC      IPC Service (Samba 3.0.2)
+        IPC$          IPC      IPC Service (Samba 3.0.12)
+        ADMIN$        IPC      IPC Service (Samba 3.0.12)
 
         Server             Comment
         ---------          -------
-        SERVER             Samba 3.0.2
+        SERVER             Samba 3.0.12
 
         Workgroup          Master
         ---------          --------
@@ -412,8 +413,8 @@
 	to install Samba on Linux, but just make sure it works without problems. There are two HP LaserJet
 	5 PS printers that are network connected.  The second printer is to be used for general
 	office and letter printing. Your recommendation to allow only the Linux server to print directly
-	to the printers was accepted. You have supplied SUSE Enterprise Linux Server version 8.0 and
-	have upgraded Samba to version 3.0.2.
+	to the printers was accepted. You have supplied SUSE Enterprise Linux Server 9 and
+	have upgraded Samba to version 3.0.12.
 	</para>
 
 		<sect3>
@@ -499,7 +500,7 @@
 
 		<para>
 		It is assumed that the server is fully installed and ready for configuration of
-		Samba 3.0.2 and for necessary support files. All TCP/IP addresses should be hard coded.
+		Samba 3.0.12 and for necessary support files. All TCP/IP addresses should be hard coded.
 		In our case, the IP address of the Samba server is 192.168.1.1 and the netmask is
 		255.255.255.0. The host name of the server used was <constant>server</constant>.
 		The office network is built as shown in <link linkend="charitynet"/>.
@@ -944,7 +945,7 @@ C:\WINDOWS: regedit ME-dpwc.reg
 	<para><indexterm>
 	    <primary>Red Hat Linux</primary>
 	  </indexterm>
-	The new server will run Red Hat Linux 9.0. You should install Samba-3.0.2 and 
+	The new server will run Red Hat Linux 9.0. You should install Samba-3.0.12 and 
 	copy all files off the old system to the new one. The existing Windows NT4 server has a parallel
 	port HP LaserJet 4 printer that is shared by all. The printer driver is installed on each
 	workstation. You must not change anything on the workstations. Mr. Meany gave instructions to
@@ -972,8 +973,8 @@ C:\WINDOWS: regedit ME-dpwc.reg
 			</para>
 
 			<para>
-			You have finished configuring the new hardware and have just completed installation of Red Hat Linux
-			9.0. Roll up your sleeves and let's get to work.
+			You have finished configuring the new hardware and have just completed installation of Red Hat 
+			Fedora Core2. Roll up your sleeves and let's get to work.
 			</para>
 
 		</sect3>
diff --git a/docs/Samba-Guide/Chap03-TheSmallOffice.xml b/docs/Samba-Guide/Chap03-TheSmallOffice.xml
index 9baa6036fc..e96dbbdac3 100644
--- a/docs/Samba-Guide/Chap03-TheSmallOffice.xml
+++ b/docs/Samba-Guide/Chap03-TheSmallOffice.xml
@@ -152,7 +152,7 @@
 	</itemizedlist>
 
 	<para>
-	In this instance the installed Linux system is assumed to be a Red Hat Linux 9.0 server 
+	In this instance the installed Linux system is assumed to be a Red Hat Linux Fedora Core2 server 
 	(as in <link linkend="AccountingOffice"/>).
 	
 	</para>
@@ -815,7 +815,7 @@ $rootprompt; ps ax | grep winbind
 
         Server               Comment
         ---------            -------
-        SLEETH               Samba 3.0.2
+        SLEETH               Samba 3.0.12
 
         Workgroup            Master
         ---------            -------
@@ -989,7 +989,7 @@ smb: \> q
 
 		<para>
 		In this network design and implementation exercise, you have created a Windows NT4 style Domain
-		Controller using Samba-3.0.2. As a result of following these guidelines meant that you experienced
+		Controller using Samba-3.0.12. As a result of following these guidelines meant that you experienced
 		and implemented several important aspects of Windows networking. In the next chapter of this book,
 		you build on the experience gained. These are the highlights from this chapter:
 		</para>
diff --git a/docs/Samba-Guide/Chap04-SecureOfficeServer.xml b/docs/Samba-Guide/Chap04-SecureOfficeServer.xml
index bd6f477ccc..06d52c08b7 100644
--- a/docs/Samba-Guide/Chap04-SecureOfficeServer.xml
+++ b/docs/Samba-Guide/Chap04-SecureOfficeServer.xml
@@ -852,10 +852,10 @@ echo -e "\nNAT firewall done.\n"
 	<procedure>
 		<step><para>
 		Install the Samba-3 binary RPM from the Samba-Team FTP site. Assuming that the binary
-		RPM file is called <filename>samba-3.0.2-1.i386.rpm</filename>, one way to install this
+		RPM file is called <filename>samba-3.0.12-1.i386.rpm</filename>, one way to install this
 		file is as follows:
 <screen>
-&rootprompt; rpm -Uvh samba-3.0.2-1.i386.rpm
+&rootprompt; rpm -Uvh samba-3.0.12-1.i386.rpm
 </screen>
 		This operation must be performed while logged in as the <command>root</command> user.
 		Successful operation is clearly indicated. If this installation should fail for any reason,
@@ -1986,13 +1986,13 @@ $rootprompt; ps ax | grep winbind
 
         Sharename      Type      Comment
         ---------      ----      -------
-        IPC$           IPC       IPC Service (Samba 3.0.2)
+        IPC$           IPC       IPC Service (Samba 3.0.12)
         netlogon       Disk      Network Logon Service
         profiles       Disk      Profile Share
         accounts       Disk      Accounting Files
         service        Disk      Financial Services Files
         apps           Disk      Application Files
-        ADMIN$         IPC       IPC Service (Samba 3.0.2)
+        ADMIN$         IPC       IPC Service (Samba 3.0.12)
         hplj6a         Printer   hplj6a
         hplj6f         Printer   hplj6f
         qmsa           Printer   qmsa
@@ -2000,7 +2000,7 @@ $rootprompt; ps ax | grep winbind
 
         Server               Comment
         ---------            -------
-        DIAMOND              Samba CVS 3.0.2
+        DIAMOND              Samba CVS 3.0.12
 
         Workgroup            Master
         ---------            -------
diff --git a/docs/Samba-Guide/Chap05-500UserNetwork.xml b/docs/Samba-Guide/Chap05-500UserNetwork.xml
index f1f36831af..8ad8d81573 100644
--- a/docs/Samba-Guide/Chap05-500UserNetwork.xml
+++ b/docs/Samba-Guide/Chap05-500UserNetwork.xml
@@ -316,7 +316,7 @@
 	<title>Implementation</title>
 
 	<para>
-	The following configuration process begins following installation of Red Hat Linux 9.0 on the
+	The following configuration process begins following installation of Red Hat Fedora Core2 on the
 	three servers shown in the network topology diagram in <link linkend="chap05net"/>. You have
 	selected hardware that is appropriate to the task.
 	</para>
diff --git a/docs/Samba-Guide/Chap07-2000UserNetwork.xml b/docs/Samba-Guide/Chap07-2000UserNetwork.xml
index 5e2af76006..dac023f4a6 100644
--- a/docs/Samba-Guide/Chap07-2000UserNetwork.xml
+++ b/docs/Samba-Guide/Chap07-2000UserNetwork.xml
@@ -388,7 +388,7 @@
 	    the logon protocols and principles of operation are
 	    concerned. The following information pertains exclusively to the
 	    interaction between a Windows XP Professional workstation and a
-	    Samba-3.0.2 server. In the discussion that follows, use is made of
+	    Samba-3.0.12 server. In the discussion that follows, use is made of
 	    DHCP and WINS.</para>
 
 	  <para>As soon as the Windows workstation starts up, it obtains an
diff --git a/docs/Samba-Guide/Chap09-AddingUNIXClients.xml b/docs/Samba-Guide/Chap09-AddingUNIXClients.xml
index 0755f7cd55..95fa2d947a 100644
--- a/docs/Samba-Guide/Chap09-AddingUNIXClients.xml
+++ b/docs/Samba-Guide/Chap09-AddingUNIXClients.xml
@@ -1505,7 +1505,7 @@ logonCount: 13
 sAMAccountName: fran$
 sAMAccountType: 805306369
 operatingSystem: Samba
-operatingSystemVersion: 3.0.2-SUSE
+operatingSystemVersion: 3.0.12-SUSE
 dNSHostName: fran
 userPrincipalName: HOST/fran@LONDON.ABMAS.BIZ
 servicePrincipalName: CIFS/fran.london.abmas.biz
@@ -1653,7 +1653,7 @@ data = "\00\00\00\00bp\00\00\06krbtgt\06krbtgt-
 <smbconfoption><name>unix charset</name><value>LOCALE</value></smbconfoption>
 <smbconfoption><name>workgroup</name><value>LONDON</value></smbconfoption>
 <smbconfoption><name>realm</name><value>LONDON.ABMAS.BIZ</value></smbconfoption>
-<smbconfoption><name>server string</name><value>Samba 3.0.2</value></smbconfoption>
+<smbconfoption><name>server string</name><value>Samba 3.0.12</value></smbconfoption>
 <smbconfoption><name>security</name><value>ADS</value></smbconfoption>
 <smbconfoption><name>username map</name><value>/etc/samba/smbusers</value></smbconfoption>
 <smbconfoption><name>log level</name><value>1</value></smbconfoption>
diff --git a/docs/Samba-Guide/Chap12-Appendix.xml b/docs/Samba-Guide/Chap12-Appendix.xml
index 22e05116f3..fc3f44a523 100644
--- a/docs/Samba-Guide/Chap12-Appendix.xml
+++ b/docs/Samba-Guide/Chap12-Appendix.xml
@@ -259,7 +259,7 @@ Paths:
 	If you wish to locate the Samba version, just run:
 <screen>
 &rootprompt; /path-to-binary-file/smbd -V
-Version 3.0.2-SUSE
+Version 3.0.12-SUSE
 </screen>
 	</para>
 
@@ -271,15 +271,15 @@ Version 3.0.2-SUSE
 	</indexterm>
 <screen>
 &rootprompt; rpm -qa | grep samba
-samba3-pdb-3.0.2-1
-samba3-vscan-0.3.4-0
-samba3-winbind-3.0.2-1
-samba3-3.0.2-1
-samba3-python-3.0.2-1
-samba3-utils-3.0.2-1
-samba3-doc-3.0.2-1
-samba3-client-3.0.2-1
-samba3-cifsmount-3.0.2-1
+samba3-pdb-3.0.12-1
+samba3-vscan-0.3.5-0
+samba3-winbind-3.0.12-1
+samba3-3.0.12-1
+samba3-python-3.0.12-1
+samba3-utils-3.0.12-1
+samba3-doc-3.0.12-1
+samba3-client-3.0.12-1
+samba3-cifsmount-3.0.12-1
 	</screen><indexterm>
 	  <primary>package names</primary>
 	</indexterm>