* merge fixes for SGML syntax errors (does no one ever regenerate the docs?)

* regenerate the docs
* add some files from SAMBA_3_0
(This used to be commit 1af74785f334bd84b2d62e7fc2975f9477386acb)

1 files changed, 15 insertions, 28 deletions

diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html
index cc703d217f..8c597e001f 100644
--- a/docs/htmldocs/browsing-quick.html
+++ b/docs/htmldocs/browsing-quick.html
@@ -5,7 +5,8 @@
 >Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="SAMBA Project Documentation"
 HREF="samba-howto-collection.html"><LINK
@@ -13,8 +14,8 @@ REL="UP"
 TITLE="General installation"
 HREF="introduction.html"><LINK
 REL="PREVIOUS"
-TITLE="Oplocks"
-HREF="oplocks.html"><LINK
+TITLE="Improved browsing in samba"
+HREF="improved-browsing.html"><LINK
 REL="NEXT"
 TITLE="LanMan and NT Password Encryption in Samba"
 HREF="pwencrypt.html"></HEAD
@@ -45,7 +46,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="oplocks.html"
+HREF="improved-browsing.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -72,9 +73,7 @@ WIDTH="100%"></DIV
 CLASS="CHAPTER"
 ><H1
 ><A
-NAME="BROWSING-QUICK"
-></A
->Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
+NAME="BROWSING-QUICK">Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
 ><P
 >This document should be read in conjunction with Browsing and may
 be taken as the fast track guide to implementing browsing across subnets
@@ -86,9 +85,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN393"
-></A
->4.1. Discussion</H1
+NAME="AEN377">3.1. Discussion</H1
 ><P
 >Firstly, all MS Windows networking is based on SMB (Server Message
 Block) based messaging. SMB messaging is implemented using NetBIOS. Samba
@@ -132,9 +129,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN401"
-></A
->4.2. Use of the "Remote Announce" parameter</H1
+NAME="AEN385">3.2. Use of the "Remote Announce" parameter</H1
 ><P
 >The "remote announce" parameter of smb.conf can be used to forcibly ensure
 that all the NetBIOS names on a network get announced to a remote network.
@@ -183,16 +178,14 @@ name resolution problems and should be avoided.</P
 ></DD
 ></DL
 ></DIV
->&#13;</P
+></P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN415"
-></A
->4.3. Use of the "Remote Browse Sync" parameter</H1
+NAME="AEN399">3.3. Use of the "Remote Browse Sync" parameter</H1
 ><P
 >The "remote browse sync" parameter of smb.conf is used to announce to
 another LMB that it must synchronise it's NetBIOS name list with our
@@ -212,9 +205,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN420"
-></A
->4.4. Use of WINS</H1
+NAME="AEN404">3.4. Use of WINS</H1
 ><P
 >Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
 recommended. Every NetBIOS machine registers it's name together with a
@@ -274,9 +265,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN431"
-></A
->4.5. Do NOT use more than one (1) protocol on MS Windows machines</H1
+NAME="AEN415">3.5. Do NOT use more than one (1) protocol on MS Windows machines</H1
 ><P
 >A very common cause of browsing problems results from installing more than
 one protocol on an MS Windows machine.</P
@@ -304,9 +293,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN437"
-></A
->4.6. Name Resolution Order</H1
+NAME="AEN421">3.6. Name Resolution Order</H1
 ><P
 >Resolution of NetBIOS names to IP addresses can take place using a number
 of methods. The only ones that can provide NetBIOS name_type information
@@ -401,7 +388,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="oplocks.html"
+HREF="improved-browsing.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -429,7 +416,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Oplocks</TD
+>Improved browsing in samba</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"